[
https://issues.apache.org/jira/browse/ARTEMIS-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Klimczak updated ARTEMIS-2675:
------------------------------------
Priority: Major (was: Critical)
> No retry button in web console for messages in auto-created DLQs
> ----------------------------------------------------------------
>
> Key: ARTEMIS-2675
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2675
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.12.0
> Reporter: Piotr Klimczak
> Priority: Major
>
> Retry button is not showing up as an option for messages in auto-created DLQs.
> Instead "Resend" button is presented.
> Config:
> {code:java}
> <?xml version='1.0'?>
> <configuration xmlns="urn:activemq"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xi="http://www.w3.org/2001/XInclude";
> xsi:schemaLocation="urn:activemq
> /schema/artemis-configuration.xsd">
> <core xmlns="urn:activemq:core"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="urn:activemq:core ">
> <name>0.0.0.0</name>
> <jmx-management-enabled>true</jmx-management-enabled>
> <persistence-enabled>true</persistence-enabled>
> <!-- this could be ASYNCIO, MAPPED, NIO
> ASYNCIO: Linux Libaio
> MAPPED: mmap files
> NIO: Plain Java Files
> -->
> <journal-type>NIO</journal-type>
> <paging-directory>data/paging</paging-directory>
> <bindings-directory>data/bindings</bindings-directory>
> <journal-directory>data/journal</journal-directory>
>
> <large-messages-directory>data/large-messages</large-messages-directory>
> <journal-datasync>true</journal-datasync>
> <journal-min-files>2</journal-min-files>
> <journal-pool-files>10</journal-pool-files>
> <journal-device-block-size>4096</journal-device-block-size>
> <journal-file-size>10M</journal-file-size>
> <!--
> This value was determined through a calculation.
> Your system could perform 25 writes per millisecond
> on the current journal configuration.
> That translates as a sync write every 40000 nanoseconds.
> Note: If you specify 0 the system will perform writes directly to
> the disk.
> We recommend this to be 0 if you are using journalType=MAPPED
> and journal-datasync=false.
> -->
> <journal-buffer-timeout>40000</journal-buffer-timeout>
> <!--
> When using ASYNCIO, this will determine the writing queue depth for
> libaio.
> -->
> <journal-max-io>1</journal-max-io>
> <!--
> You can verify the network health of a particular NIC by specifying
> the <network-check-NIC> element.
> <network-check-NIC>theNicName</network-check-NIC>
> -->
> <!--
> Use this to use an HTTP server to validate the network
>
> <network-check-URL-list>http://www.apache.org</network-check-URL-list> -->
> <!-- <network-check-period>10000</network-check-period> -->
> <!-- <network-check-timeout>1000</network-check-timeout> -->
> <!-- this is a comma separated list, no spaces, just DNS or IPs
> it should accept IPV6
> Warning: Make sure you understand your network topology as this
> is meant to validate if your network is valid.
> Using IPs that could eventually disappear or be
> partially visible may defeat the purpose.
> You can use a list of multiple IPs, and if any
> successful ping will make the server OK to continue running -->
> <!-- <network-check-list>10.0.0.1</network-check-list> -->
> <!-- use this to customize the ping used for ipv4 addresses -->
> <!-- <network-check-ping-command>ping -c 1 -t %d
> %s</network-check-ping-command> -->
> <!-- use this to customize the ping used for ipv6 addresses -->
> <!-- <network-check-ping6-command>ping6 -c 1
> %2$s</network-check-ping6-command> -->
> <!-- how often we are looking for how many bytes are being used on
> the disk in ms -->
> <disk-scan-period>5000</disk-scan-period>
> <!-- once the disk hits this limit the system will block, or close
> the connection in certain protocols
> that won't support flow control. -->
> <max-disk-usage>90</max-disk-usage>
> <!-- should the broker detect dead locks and other issues -->
> <critical-analyzer>true</critical-analyzer>
> <critical-analyzer-timeout>120000</critical-analyzer-timeout>
> <critical-analyzer-check-period>60000</critical-analyzer-check-period>
> <critical-analyzer-policy>HALT</critical-analyzer-policy>
> <page-sync-timeout>40000</page-sync-timeout>
> <global-max-size>100Mb</global-max-size>
> <wildcard-addresses>
> <routing-enabled>true</routing-enabled>
> <any-words>></any-words>
> </wildcard-addresses>
> <security-settings>
> <security-setting match=">">
> <permission type="createNonDurableQueue" roles="amq"/>
> <permission type="deleteNonDurableQueue" roles="amq"/>
> <permission type="createDurableQueue" roles="amq"/>
> <permission type="deleteDurableQueue" roles="amq"/>
> <permission type="createAddress" roles="amq"/>
> <permission type="deleteAddress" roles="amq"/>
> <permission type="consume" roles="amq"/>
> <permission type="browse" roles="amq"/>
> <permission type="send" roles="amq"/>
> <!-- we need this otherwise ./artemis data imp wouldn't work
> -->
> <permission type="manage" roles="amq"/>
> </security-setting>
> </security-settings>
> <address-settings>
> <!-- if you define auto-create on certain queues, management has
> to be auto-create -->
> <address-setting match="activemq.management>">
> <dead-letter-address>DLQ</dead-letter-address>
> <expiry-address>ExpiryQueue</expiry-address>
> <redelivery-delay>0</redelivery-delay>
> <!-- with -1 only the global-max-size is in use for limiting
> -->
> <max-size-bytes>-1</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> <!--default for catch all-->
> <address-setting match=">">
> <dead-letter-address>DLQ</dead-letter-address>
> <expiry-address>ExpiryQueue</expiry-address>
> <redelivery-delay>2000</redelivery-delay>
> <!-- with -1 only the global-max-size is in use for limiting
> -->
> <max-size-bytes>-1</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <address-full-policy>PAGE</address-full-policy>
> <expiry-queue-prefix>EXP.</expiry-queue-prefix>
> <dead-letter-queue-prefix>DLQ.</dead-letter-queue-prefix>
>
> <auto-create-dead-letter-resources>true</auto-create-dead-letter-resources>
>
> <auto-create-expiry-resources>true</auto-create-expiry-resources>
> <auto-create-queues>true</auto-create-queues>
> <auto-create-addresses>true</auto-create-addresses>
> <auto-create-jms-queues>true</auto-create-jms-queues>
> <auto-create-jms-topics>true</auto-create-jms-topics>
> </address-setting>
> </address-settings>
> <addresses>
> <address name="DLQ">
> <multicast>
> <!-- As Artemis is using dynamic DLQ creation, where
> every DLQ uses filters, that one will have no filter therefore it will
> receive them all -->
> <queue name="DLQAlerts" />
> </multicast>
> </address>
> <address name="ExpiryQueue"/>
> </addresses>
> <acceptors>
> <!-- useEpoll means: it will use Netty epoll if you are on a
> system (Linux) that supports it -->
> <!-- amqpCredits: The number of credits sent to AMQP producers -->
> <!-- amqpLowCredits: The server will send the # credits specified
> at amqpCredits at this low mark -->
> <!-- amqpDuplicateDetection: If you are not using duplicate
> detection, set this to false
> as duplicate detection requires
> applicationProperties to be parsed on the server. -->
> <!-- amqpMinLargeMessageSize: Determines how many bytes are
> considered large, so we start using files to hold their data.
> default: 102400, -1 would mean to
> disable large mesasge control -->
> <!-- Note: If an acceptor needs to be compatible with HornetQ
> and/or Artemis 1.x clients add
> "anycastPrefix=jms.queue.;multicastPrefix=jms.topic."
> to the acceptor url.
> See https://issues.apache.org/jira/browse/ARTEMIS-1644
> for more information. -->
> <!-- Acceptor for every supported protocol -->
> <acceptor
> name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true</acceptor>
> </acceptors>
> <!-- Uncomment the following if you want to use the Standard
> LoggingActiveMQServerPlugin pluging to log in events
> <broker-plugins>
> <broker-plugin
> class-name="org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin">
> <property key="LOG_ALL_EVENTS" value="true"/>
> <property key="LOG_CONNECTION_EVENTS" value="true"/>
> <property key="LOG_SESSION_EVENTS" value="true"/>
> <property key="LOG_CONSUMER_EVENTS" value="true"/>
> <property key="LOG_DELIVERING_EVENTS" value="true"/>
> <property key="LOG_SENDING_EVENTS" value="true"/>
> <property key="LOG_INTERNAL_EVENTS" value="true"/>
> </broker-plugin>
> </broker-plugins>
> -->
> </core>
> </configuration> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
