Re: [JBoss-user] AbstractInstanceCache deadlock

2003-07-21 Thread Andrew May
: Friday, July 18, 2003 10:06 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] AbstractInstanceCache deadlock We patched this into production about half and hour ago, and went back to 300 for the overager period. If you don't hear from me on Monday you'll know it's worked :) Thanks for the quick patch

Re: [JBoss-user] AbstractInstanceCache deadlock

2003-07-18 Thread Andrew May
] Subject: Re: [JBoss-user] AbstractInstanceCache deadlock It can be disabled by a large number that will cause overflow of the 2^31 value when converted from seconds to milliseconds as this will result in a negative period. For example: overager-period214748364/overager-period

RE: [JBoss-user] AbstractInstanceCache deadlock

2003-07-18 Thread Bill Burke
To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] AbstractInstanceCache deadlock We patched this into production about half and hour ago, and went back to 300 for the overager period. If you don't hear from me on Monday you'll know it's worked :) Thanks for the quick patch and the advice

[JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Andrew May
Hi, We've just release a production service using JBoss 3.2.1 on Solaris with Sun's 1.4.2 JVM, and we're seeing a deadlock on the AbstractInstanceCache for one of our stateful session beans that's used heavily. Over a period of time more and more threads become locked trying to insert or get

RE: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Bill Burke
Examining now. Thanks for the thread dump as I would not be able to investigate without. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew May Sent: Thursday, July 17, 2003 9:32 AM To: [EMAIL PROTECTED] Subject: [JBoss-user

RE: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Bill Burke
PROTECTED] Subject: [JBoss-user] AbstractInstanceCache deadlock Hi, We've just release a production service using JBoss 3.2.1 on Solaris with Sun's 1.4.2 JVM, and we're seeing a deadlock on the AbstractInstanceCache for one of our stateful session beans that's used heavily. Over a period

Re: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Andrew May
: Thursday, July 17, 2003 9:32 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] AbstractInstanceCache deadlock Hi, We've just release a production service using JBoss 3.2.1 on Solaris with Sun's 1.4.2 JVM, and we're seeing a deadlock on the AbstractInstanceCache for one of our stateful session beans

RE: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Bill Burke
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew May Sent: Thursday, July 17, 2003 9:32 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] AbstractInstanceCache deadlock Hi, We've just release a production service using JBoss 3.2.1 on Solaris with Sun's 1.4.2 JVM, and we're

Re: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Scott M Stark
It can be disabled by a large number that will cause overflow of the 2^31 value when converted from seconds to milliseconds as this will result in a negative period. For example: overager-period214748364/overager-period -- Scott Stark Chief Technology Officer JBoss

RE: [JBoss-user] AbstractInstanceCache deadlock

2003-07-17 Thread Bill Burke
Ok, it is fixed in Branch_3_2 and HEAD. The fix is in LRUEnterpriseContextCachePolicy.java Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott M Stark Sent: Thursday, July 17, 2003 1:26 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user