David, unfortunately I am behind a firewall here, and cannot yet get access to CVS, but we are working on this. As soon as we get access I will explore the CVS code.
My test is non-proprietary, and here it is. Its not the prettiest test but it does the trick. I deploy it as an MBean in a .sar file and kick it off via the JMX console. The database table MESSAGE has two columns, MESSAGE_ID is an autoincrementing identity numeric field, MESSAGE_TEXT a varchar(200) field. I use MQSeries as the JMS provider, with queue names JBossMQJmsQ1 and JBossMQJmsQ2. The test moves messages between the two queues and the table repreatedly in three different threads, each with their own transactions. As a warning, it takes about 2 1/2 hours to fall over, although in another test I've added more threads and tables to get the transactions quicker. I haven't done this test with any other JMS or database providers under XA transactional control. I have seen on a bulletin board someone complaining of something vaguely similar under Weblogic and SQL Server, but they didn't give enough detail for me to say for sure that its the same thing. thanks, Steve. <<XATransactionTest.java>> <<XATransactionTestMBean.java>>
XATransactionTest.java
Description: Binary data
XATransactionTestMBean.java
Description: Binary data
