when one service method which has tx setting as propagation="REQUIRES_NEW" invokes another service method with the same settings, does the second method use the same session or does it create a new one(assuming the default contextual settings are used)? If not what decides whether a new session is opened or the existing one is used in the invoked method, it would be great if someone can make this clear. thanks,


regards
Aravias

if you use REQUIRES_NEW, the container always create a new transaction. If the client already has a transaction, it's temporarily suspended until the method returns.
It means that the success of failure of the new transaction has no effect on the existing transaction.

Thanks for the reply.I understand that part but what I am not able to figure out is whether the same session is used or does it create a new one when u say requires_new, I guess if its the same thread then its uses the suspended transactions session otherwise it creates its own session.What is the default settings for Contextual sessions in hibernate, does each thread which creates a session make it available for other transactions spawned from that same thread or does it have to be set explicitly to do that?