This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
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?