Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Carrying transactions over 2 application servers?

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?


With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic