-
1. Re: org.jboss.cache.lock.TimeoutException on using transacti
brian.stansberry Jan 29, 2006 9:09 PM (in response to stelang)I wouldn't call this an "issue"; this is exactly the behavior you'd expect when one thread acquires a write lock on a resource and then holds it, while another thread tries to acquire the lock. The 2nd thread times out and throws an exception because the first thread is sleeping with the lock held. If you use transactions, locks are held for the life of the transaction.
If you want this to work, you need to set your LockAcquisitionTimeout to > 15 seconds. -
2. Re: org.jboss.cache.lock.TimeoutException on using transacti
stelang Jan 30, 2006 6:01 PM (in response to stelang)Thanks for your response. I have increased the lockacquisition timeout to 50 seconds, but still get the timeout exception after 30sec. Shouldn't the 2nd servlet wait for atleast 50seconds to acquire lock on the object before timing out?
-
3. Re: org.jboss.cache.lock.TimeoutException on using transacti
manik Feb 1, 2006 5:37 AM (in response to stelang)It should - what version of JBossCache are you using, the exception should print out how many seconds it waited before it threw a TimeoutException ...
-
4. Re: org.jboss.cache.lock.TimeoutException on using transacti
stelang Feb 1, 2006 9:52 AM (in response to stelang)I am using Jbosscache1.2.3. It prints the exact exception which I have posted here. To determine the time taken before it throws the exception, I had put debug statements in my code..before the "put statement" and in my catch block in the 2nd servlet. This time difference was 30s. Thanks.