actually, it *was* partially a jbossmq bug. i'd say that the messages getting committed on rollback was most certainly a jbossmq problem.
i am indeed pursuing the problem from the oracle side of things. apparently you have some crystal ball and can tell that the jboss transaction manager is communicating correctly with oracle and the only possible cause of the problem is oracle! i, unfortunately, can't verify that jboss is not at fault, so i'll continue to pursue the problem from both ends until i get a fix. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911947#3911947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911947 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
