From: Scott M Stark <scott.stark@jb...> - 2005-11-28 23:03:34
Profiling of specj runs was showing a java lock contention resulting
from a toString call from within the TransactionImpl.lock call, so this
is either the log.debug or the IllegalStateException. I started with the
log call so we redo the profile ourselves as this profile was run by a
partner. I can send the jrockit jra output once I get it. The current
snapshot view I have only starts with the TransactionImpl.lock call.
> -----Original Message-----
> From: Adrian Brock=20
> Sent: Monday, November 28, 2005 1:55 PM
> To: Scott M Stark
> Cc: jboss-development@...
> Subject: Transaction Lock Contention?=20
> Re:boss-transaction/src/main/org/jboss/tm ...
> What brought this up?
> Lock contention on a transaction across threads represents a=20
> more serious problem!
> This used to be a WARN until I tested/added support for using=20
> a transaction concurrently on multiple treads.
> That is unless you are deliberately trying to use a=20
> transaction multi-threadedly (if that is a word :-)?
> It certainly shouldn't be happening for EJBs. It is not allowed!