Hi

Does anyone have experience with bean managed persistence in transactions.
In my case, I have a stateless session bean which modified two BMP entity
beans.  Upon modification of the second entity bean, a failure should result
in rollback of the entire uncommitted transaction.  I'm finding this is not
happening, and the server is printing out TRANSACTION ROLLBACK EXCEPTION
along with the original system error.  I have tried both declarative
transaction management and explicit (begin, commit, rollback) and neither
seems to work.  I should mention, I have an example of a stateful session
bean which inserts into two tables and publishes via JMS all in a
transaction spread over several calls to the bean and this does work
properly, so it doesn't seem to be configuration related.

Any help would be appreciated.  Does anyone have experience with BMP and
transactions specifically?

Thanks

Eric

Attachment: winmail.dat
Description: application/ms-tnef

Reply via email to