Red Hat Bugzilla – Bug 998621
QueueBrowser created on local transacted session removes messages from queue
Last modified: 2015-01-04 17:56:59 EST
Description of problem: When QueueBrowser is created on a session with transactions, it removes messages from queue. Version-Release number of selected component (if applicable): qpid-jca-0.18-8.el6.noarch qpid-cpp-server-0.18-14.el6.i686 How reproducible: random - needs to be called several times Steps to Reproduce: 1. Create transacted session 2. create queue browser 3. in a loop check number of messages in queue Actual results: at some point messages are removed from queue like queue dur autoDel excl msg msgIn msgOut bytes bytesIn bytesOut cons bind ========================================================================================================================= 2adf18ed-77ce-4e8d-bfc0-8429174937f0:0.0 Y Y 0 0 0 0 0 0 1 2 mrg_localtx_out 8 486 478 466 12.0k 11.6k 0 1 Sometimes it also removes from queue more messages than there actually were (please see Bug 997065) Expected results: no messages are removed from queue Additional info:
For this BZ and https://bugzilla.redhat.com/show_bug.cgi?id=998628 I need a bit more information: 1) Are you using the LocalTransactionCF in your *-ds.xml file (please attach your configuration). 2)How are you running this test? What sort of application component (EJB, Servlet etc) are you using? Is there an active XA transaction while you are running this (this would have an effect).
If we could test with the Java client outside of the app server, that would be good as well. I can setup the code to do this.
Confirmed and verified behavior. Looking into it further...good catch Val.
I answered question to Weston earlier in a private conversation as: 1) The whole test runs on local transactions with eap6. 2) EJB, Servlet are involved. No active XA transactions is running while test runs.
Tested on EAP5 with local transactions. Same behaviour as Valentina described.
Confirmed as well on EAP5. Since this ultimately involves the JMS client, it will persist across EAP versions independent of JCA/JEE server.
Making this a qpid-java bug. Please return it to qpid-jca if that's incorrect.
The issue is no longer present in version 2.3 (as the result of release 2.3.6)