HI all,
I've been digging deep into code of hibernate / jboss jta / transaction manager stuff.
I doscovered that jta transaction is kept as tread local, and tomcat
( integrated with jboss ) reuses threads ( possibly containing stale transaction in thread local )
So I have couple of questions - ok, I have 2 separate hibernate session factories inside my application - one coming from osuser,
and another from my persistence stuff ( there will be more in future ) ,
and both of them are used in the same request.
So, both of them share the same jta transaction? ( jndi name
for user transaction is default one )
If one ot sesions is stale ( for example soem exception ) and I
follow guidelines of rolling back transaction ( which I'm starting when
acquiring session ) and discarding session - then another session
session factory will refer to the same rolled back transaction?
Is there the way to kill that transaction for ever?
Or am I better off with jdbc transactions for separate session factories? ( ok, sesion factories belong to different portal application, so it could be option for me )
_________________ Got new hibernate xdoclet plugin? http://www.sourceforge.net/projects/xdoclet-plugins/
... Momentan auf der Suche nach neuen Projekt ode Festanstellung....
|