Atomikos Forum

I tried updating from 3.3.1 to 3.3.4 and it seems atomikos is now swallowing underlying DB exceptions.

I have some java tests which attempt to explicitly violate some database constraints, catch the exception, and inspect the exception to verify that the correct database constraint error occurred.  Unfortunately, with 3.3.4, the jdbc exceptions seem to be replaced by jta rollback exceptions, but the underlying exception doesnt seem to include the underlying exception :(

Im wondering, am I doing something incorrectly, or is there some other way to get at the underlying exception that I'm not aware of?

Thanks!
- Phillip

Hi,

Can you post:

1 - your code
2 - what you used to see in 3.3.1
3 - what you are seeing now?

Thanks

Actually I think this is a non-issue actually.  I am currently using atomikos as a jta transaction manager for running tests outside of an ejb/servlet container.

I ran the tests inside glassfish and it actually has the same behavior as these later atomikos versions do now.  It's actually a disappointing behavior on the part of JEE the way that it wraps the underlying exceptions and does no chaining, but it seems to be a known problem and there are known ways to work around it so I'm content :)

Thanks!
- Phillip