[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1440) JTA-prepared message delivered to other consumer.

JTA-prepared message delivered to other consumer. -------------------------------------------------- Key: JBMESSAGING-1440 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1440 Project: JBoss Messaging Issue Type: Bug Environment: JBoss 4.2.2 + JBM 1.4.0.SP3. Windows XP. Reporter: szhigunov Assignee: Tim Fox Attachments: myxatest.zip The problem is that when fully prepared tx1 fails in the commit phase, JBM delivers the message second time in tx2, while tx1 is still in progress. Eventually recovery commits tx1, so the message gets delivered and committed twice. The attached test (myxatest.zip) is a clean JBoss 4.2.2 + JBM 1.4.0 SP3 with my test MBean: jboss-4.2.2.GA\server\messaging\lib\myxatest.jar (code and source) + jboss-4.2.2.GA\server\messaging\deploy\myxatest-service.xml. Steps to reproduce the problem: 1. Start the server. 2. Go to JMX console + myxatest + service=Test. Invoke send. 3. Go to JMX console + jboss.messaging.destination + name=A.service=Queue. Verify MessageCount=1. 4. Go to JMX console + myxatest + service=Test. Invoke receive. That will start XA transaction; enlist DummyXAResource; get JMS connection from JCA and receive message. DummyXAResource sleeps 60 sec inside the commit call. 5. Verify that DummyXAResource prints "DummyXAResource commit start sleeping for 60 sec" message. 6. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke stop(). Check that DummyXAResource finished commit and printed "DummyXAResource commit end" message. JBM commit fails. 7. Now we have fully prepared JBM transaction in progress. You can see one record in JBM_TX. 8. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke start(). 9. Go to JMX console + myxatest + service=Test. Invoke receive again. Same message delivered again. And this is wrong. Wait for a minute and let transaction finish successfully. 10. Got to JBM_TX and verify that transaction is still there (nobody recovered it!). 11. Stop server, enable JBM recovery, start server. In couple minutes the original transaction is found and committed (second time). JBM_TX is empty.