Container-managed Transaction Demarcation

[franktv]

Pardon the newbie question ... but can someone clarify something for me?

Using "container-managed transaction demarcation" within any bean-type (session or entity), what triggers a rollback of the transaction in JBoss? I am assuming that any "exception" within a transactional-aware method on a bean will trigger a rollback ... am I right in this assumption? Given that logic, can a rollback be forced by programatically throwing any exception in the bean's method? Thanks for any feedback!

- Frank

[davidjencks]

I'm not exactly sure which exceptions trigger a rollback... I kind of think no exceptions you can generate... but I'm not sure. What will force a rollback is calling setRollbackOnly() on the EJBContext you got in the SetEntityContext method (or setSessionContext)

[franktv]

Thanks for the response David!

I now understand the difference between "System" exceptions and "Application" exceptions ... system exceptions (thrown by the container) cause transactions to be rolled back whereas application exceptions do not ... unless a setRollbackOnly() is called on the bean context. Thanks again!

[abuehler]

Hi, do you know what king of exception are JDBC Exceptions ? Like if i do a RAISERROR in a StoredProcedure or something?! (MSSQL2k)