This is a problem I've faced before...
It Orion, protecting your data consistency (I LOVE THIS SERVER!!!!!)
You'll see, the spirit of transaction processing is the management of
resources.
There's something known as transaction isolation, I figure that in your app
it is set to 'SERIALIZABLE'
Whenever there's stress on the server(a lotta HTTP connections targeting
dinamic pages), this kind of problem should
arise...
To avoid, try to keep your jsp code-free, that is, perform in EJB as many
work as you can, defining very granular methods( I use Stateless Session
Beans for this), then call these methods from jsp...
Another workaround, at the cost of less data consistency, is to change the
isolation level to 'COMMITED'.
If you stress test your app further, you'll discover that orion starts to
choke, eating up DB connections and not releasing them (I use CMP), refer to
bug #161 in bugzilla for a complete description
My 2c,
JP
-----Original Message-----
From: Adam Cassar [mailto:[EMAIL PROTECTED]]
Sent: Martes, 14 de Noviembre de 2000 8:55
To: Orion-Interest
Subject: DeadlockException
Does anyone know what the following error means?
11/14/00 10:51 PM Error in bean
com.netregistry.aucom.accounting.BillingAccount: Error in ejbPassivate
com.evermind.server.DeadlockException: Deadlock detected: thread 11 is
waiting for resource entity 1003 held by thread 11
Any ideas on how to track it down?
