[
https://issues.apache.org/jira/browse/AMQ-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-1726.
-----------------------------
Resolution: Cannot Reproduce
I couldn't reproduce this.
> mismatched DLQ statistic using jconsole, when message expire in Topic with
> durable subscriber
> ---------------------------------------------------------------------------------------------
>
> Key: AMQ-1726
> URL: https://issues.apache.org/jira/browse/AMQ-1726
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: Windows XP
> java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> Java HotSpot(TM) Client VM (build 1.6.0_02-b05, mixed mode, sharing)
> Reporter: Juraj Kuruc
> Fix For: NEEDS_REVIEWED
>
> Attachments: ASF.LICENSE.NOT.GRANTED--dlq.bmp,
> ASF.LICENSE.NOT.GRANTED--dlqTest.zip
>
>
> When time to live is set on producer and message expire then receive attemp
> is performed (durable Topic subscriber), message goes to ActiveMQ.DLQ. After
> second expired message statistic for DLQ size shows 3. After 3. message DLQ
> size is 6. When purge() method on DLQ is performed, jconsole fails and shows
> nothing - only reconnect to jconsole repair this state (statistic on DLQ is
> still wrong).
> Use case descr.
> 1. run ConsumerDlqTest to create durable subscription
> 2. stop ConsumerDlqTest
> 3. run ProducerDlqTest to send one message to Topic
> 4. wait 1000ms and run ConsumerDlqTest again
> 5. repeat 3.
> 6. repeat 4.
> 7. jconsole statistic for ActiveMQ.DLQ - QueueSize = 3 (while 2 messages are
> inside)
> 8. press purge() (operation on ActiveMQ.DLQ)
> result is shown on picture in attachment
> 9.reconect to activemq using jconsole
--
This message was sent by Atlassian JIRA
(v6.1#6144)
