You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org> on 2011/10/13 17:24:11 UTC
[jira] [Commented] (AMQ-3540) gcInactiveDestinations causes data
loss
[ https://issues.apache.org/jira/browse/AMQ-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126663#comment-13126663 ]
Timothy Bish commented on AMQ-3540:
-----------------------------------
Recommend you try a recent 5.6-SNAPSHOT this may already be fixed.
> gcInactiveDestinations causes data loss
> ---------------------------------------
>
> Key: AMQ-3540
> URL: https://issues.apache.org/jira/browse/AMQ-3540
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Environment: Ubuntu 11.04 64-bit
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1)
> OpenJDK Client VM (build 20.0-b11, mixed mode, sharing)
> Reporter: James Green
>
> With gcInactiveDestinations switched on we (two staffers testing) noticed some messages were being accepted by the stomp connector (stomp.log shows the trace) from our producer, yet the web interface showed the queue no longer present, and our regular client saw no message being delivered to it once subscribed (web interface naturally then showed the queue but with zero counters).
> This was reproducable no better than 20% of the time (in my non-scientific estimate of using our standard app). Our app uses the receipt header.
> I asked on the -users mailing list and someone else has reported the much the same:
> http://activemq.2283324.n4.nabble.com/Possible-Bug-quot-Deleting-inactive-destination-quot-with-pending-messages-td3229098.html
> I'll let Martin comment if he wishes. Naturally this may prove difficult to track down so if the developers could give some hints as to scenarios to test I will try and make some time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira