wood burning stoves 2.0*
The moose likes Websphere and the fly likes Carrying transactions over 2 application servers? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Carrying transactions over 2 application servers?" Watch "Carrying transactions over 2 application servers?" New topic

Carrying transactions over 2 application servers?

Joe Boxer

Joined: Oct 23, 2003
Posts: 15

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?


Consider Paul's rocket mass heater.
subject: Carrying transactions over 2 application servers?
Similar Threads
Question about Transactions in EJB / MDB scenario
long post IBM.158
please answer this 128 questions for WLS. Urgently!
MDB starts before Queue send is commited