That's interesting,
if an entity is tied in a transaction and the transaction times out how can
we make sure that the entity is notified of the event?
I guess one solution is to let new threads coming in make sure that the
transaction with the entity is not timed out...we must take care about
coding the "exit" of the first thread (i.e. if cleaned up then don't clean).
That would work but requires care in coding.
marcf
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
Burke
Sent: Tuesday, August 28, 2001 3:17 PM
To: Jboss-Development@Lists. Sourceforge. Net
Subject: [JBoss-dev] transaction timeouts broken?
JBoss uses pessimistic locking. So as an entity bean is accessed within a
transaction it is pessimistically locked.
What if the thread that is the transaction is tied up blocking forever on
I/O? Yes, the TM will mark the transaction as rolled back, but the entity
beans locked within the transaction will not be released because the thread
will never wakeup and realize it must do a rollback. Am I wrong here?
Regards,
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
