Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Carrying transactions over 2 application servers?  RSS feed

Joe Boxer
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have 2 enterprise application. Each of them is deployed on a different app server within the same node.
An session EJB from application A via a method doSomething() accesses an entity EJB in the application B.

Transaction attributes on doSomething are �transaction required�
Transaction attributes on the entity EJB are �transaction required�

The call to doSomething rolls back the transaction.
If I change the transaction attributes on the EJB to �not supported� or �required new� it works fine.

Wondering if I violate any transaction rules?
Is it not possible to share/carry a transaction over 2 app server?
Do the transaction setting only apply to transactions within one app server?
If it is not possible to carry the transaction initiated on app server A to app server B, how would I automatically roll back the transaction if it failed on the second app server? Is the only way managing the transaction programmatically?


It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!