Hi again, I repackaged the *test application* so that now *it does not require any environment setup*. Only thing is that, in order to achieve that, I had to add also the possibility to use Derby in place of MySql. I also use only one instance of ActiveMQ (in place of two used before) but the problem seems to show up anyway.
https://github.com/iannuz/TestXA-allEmbedded It should only be enough to download it and follow the instructions in README.txt If there are issues let me know. It still gives the possibility to run the same test case on the same code either in "tomee" or java-"standalone/bitronix". In second case the test case is successful in first case there are issues in the "rollback" situation. I hope that the not correct behavior in tomee comes from bad settings I did somewhere (maybe in https://github.com/iannuz/TestXA-allEmbedded/blob/master/TestXA-allEmbedded/tomee/conf/tomee.xml). Once all the processes are up the activemq UI (http://localhost:8161/admin/queues.jsp) should be available for monitoring the queues and for doing also manual testing. Messages put into "MY_INCOMING_QUEUE" that contain the text "/commit/" will be stored in db and forwarded to "MY_OUTGOING_QUEUE", those that contain the text "/rollback/" will trigger an insert in the DB, a put in the "MY_OUTGOING_QUEUE" and then a rollback. The rollback should put back the message into "MY_INCOMING_QUEUE", but since msg redelivery is set to 0 then the same message will end up in "DLQ.MY_INCOMING_QUEUE". This is exactly what the automated test case triggers and checks. Hopefully the effort I have done will allow you to reproduce the problem in just a few minutes. Thanks -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Tomee-MySql-ActiveMQ-XA-Distributed-Transactions-tp4676680p4676743.html Sent from the TomEE Users mailing list archive at Nabble.com.
