Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Shrikrishna Patil

Greenhorn
+ Follow
since Jun 08, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Shrikrishna Patil

Hi Ishwar,

This might be because of the session sharing facility of Browsers.

Refer below link, it may be helpful for you.
http://stackoverflow.com/questions/2963983/how-to-avoid-session-sharing-provided-by-ie8-programatically-in-java-j2ee-applic

7 years ago
I think we can propagate transaction across different containers.
This is also known as "two phase commit".

I think the problem amy be with the prograaming code at EJB A or EJB B.

Generally the EJBException should be propagated up to the Container.
i.e we should not catch EJBException or RemoteException, if caught it should be rethrown again, so that the container will come to know that the exception has occured and then the container will rollback transaction.
I am assuming that the container is responsible for managing transactions.