> Is there a way we can determine either from logging or some other mechanism what/when/where a transaction's state is turned to aborted?
Turn on full debugging in the jbossjta-properties.xml and ensure the com.arjuna classes log at DEBUG or TRACE in your log4j config file. Let me know when you manage to dig yourself out from under the vast quantity of output that will generate :-)
Thanks for the reply.
I see what you mean by the massive amount of logging. Would you know of a string to pick out for when a transaction gets set to the "aborted" state?
Also, I've tried attaching different version of the JTA source code to the arjuna classes and can never get an exact match on all classes.
hehe. I did warn you :-)
The trick to matching the source is to look at the build/build-thirdparty.xml file for the AS version you are running, it will tell you which version of JBossTS you need. For AS 4.2.0.GA it's TS 4.2.3.SP3 but you should really move to AS 4.2.2.GA
Thanks again for the reply.
We found the issue after turning the logging up. The transaction manager was fine, there was an underlying Oracle error being thrown out of the JMS persistence logic that was not being logged with the standard log levels.