activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-3540) gcInactiveDestinations causes data loss
Date Mon, 17 Oct 2011 21:49:10 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-3540.
-----------------------------

    Resolution: Cannot Reproduce

Test aren't showing any indication of an issue.  Recommend trying against the 5.6 SNAPSHOT
build.  If you still see an issue a JUnit test case that shows the problem would be helpful
in debugging this.
                
> 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

        

Mime
View raw message