Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

LockTimedOutException

 
shivendra dubey
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am getting "weblogic.ejb.extensions.LockTimedOutException" exception in my application. Can any one tell me what event causes this exception & what is the solution for that.
 
Steve
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We also got this error this morning on our Weblogic server (5.1 SP9). Can't find anything about that error on the Internet.
Here's what I got in the log file :
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:162)
If this can help someone to find out what can cause this error and hopefully how to resolve the problem, it will be very helpful!
By the way, after restarting the server, everything started working again...
Steve
Originally posted by shivendra dubey:
I am getting "weblogic.ejb.extensions.LockTimedOutException" exception in my application. Can any one tell me what event causes this exception & what is the solution for that.
 
shivendra dubey
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The problem starts like this, as we wanted to have reference to a stateful session bean through out the session so ew kept that object in session. Well it may be the one of the reason but dont know.
Now when user clicks 2 times on the jsp page, 2 servlet runs at a time that uses the same session reference. & when servlet tries to call any method on that bean it throws the exception.
But i really dont know how to solve this problem.
Can we increase the lock timeout for any bean or container.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic