Atomikos Forum

Hi,

Runtime exceptions thrown in the methods of Synchronization leave the transaction in a really nasty state. There is a problem with the Ecslipelink JTA which throws an exception in this way - rather than catching it and marking the transaction for rollback only.

However, I do think that Atomikos should catch all such exceptions. In before completion, the transaction should be marked for rollback. In after complextion, the exceptions should not stop other registered Synchronization's being called, since they ma have clearn up to do.

I have also raised an issue with Eclipselink, and implementation a wrapper to handle it in the mean time.

Tim Wright

Hi,

Thanks for the feedback, it sounds like we should do this indeed. I will create a case for the next release - this should not be hard to do.

Guy

Tim, would you be able to share details of the eclipselink problem?  And have you tried the latest 3.3.4 release?  I'm using eclipselink w/ atomikos transaction essentials for JTA and am interested in knowing about any related problems.

I'm having a problem as of 3.3.4 which I believe may be related to changes introduced since 3.3.1 and now I'm curious if they are all related :)

Thanks
- Phillip