Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 13 Oct 2011 08:51:11 +0000 (UTC)
From: "James Green (Created) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <679147911.8395.1318495871740.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (AMQ-3540) gcInactiveDestinations causes data loss
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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