yes we know this one... it seems that on transaction timeouts, a clean up is
forgotten.
As I mentioned to you when we met, there is a lot of new logic in PB2 and
the locking is brand new. PB1 didn't have any so you are always safe. I
recommend waiting for FINAL or PB3 for a Production upgrade. We will fix
this in the mean time
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|[EMAIL PROTECTED]
|Sent: Monday, October 09, 2000 8:06 PM
|To: jBoss
|Subject: [jBoss-User] LOCKING-WAITING in PB2?
|
|
|We just deployed PB2 on our staging system for some testing before
|replacing PB1 on our production systems. Unfortunately for the first time
|ever while using jboss an upgrade proved fatal. After running for a day or
|two (with little or no usage) we found about 6K lines of the following
|output:
|
|[MyBean] LOCKING-WAITING for id (primary key) ctx.hash 7654866 tx.hash 49
|
|The clients simply time out on operations using jboss. Has anyone else
|seen this behavior?
|
|C=)
|
|--------------------------------------------------------------------------
| The fact that no one understands you doesn't mean you're an artist.
|--------------------------------------------------------------------------
|Caskey <caskey*technocage.com> /// TechnoCage Inc.
|--------------------------------------------------------------------------
| Oh no! Space monkeys are attacking! -- eddie izzard
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
