You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Juraj Kuruc (JIRA)" <ji...@apache.org> on 2008/05/14 13:29:43 UTC
[jira] Created: (AMQ-1726) mismatched DLQ statistic using jconsole,
when message expire in Topic with durable subscriber
mismatched DLQ statistic using jconsole, when message expire in Topic with durable subscriber
---------------------------------------------------------------------------------------------
Key: AMQ-1726
URL: https://issues.apache.org/activemq/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
Attachments: dlq.bmp, 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1726) mismatched DLQ statistic using
jconsole, when message expire in Topic with durable subscriber
Posted by "Juraj Kuruc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42794#action_42794 ]
Juraj Kuruc commented on AMQ-1726:
----------------------------------
For addition to this isssue, if you try to start and stop durable consumer on Topic which had one expired message, DLQ message size increase every time.
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. run ConsumerDlqTest again
6. run ConsumerDlqTest again
Result is that DLQ size in jconsole shows 6 messages.
> mismatched DLQ statistic using jconsole, when message expire in Topic with durable subscriber
> ---------------------------------------------------------------------------------------------
>
> Key: AMQ-1726
> URL: https://issues.apache.org/activemq/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
> Attachments: dlq.bmp, 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.