View Single Post
  #2 (permalink)  
Old May 17th, 2008, 02:42
james_foran james_foran is offline
Member
 
Join Date: Dec 2007
Posts: 87
Groans: 1
Groaned at 1 Time in 1 Post
Thanks: 5
Thanked 16 Times in 16 Posts
Rep Power: 3
james_foran is on a distinguished road
Re: weblogic.ejb20.locks.LockTimedOutException

Hello Prasad,

See that error quite often in agents. Generally, it will occur when two agents are trying to access the same Java Bean, ie, an Order or Shipment.

After 300 seconds waiting for the Java Bean, OTM will throw this error.

The first place I would be looking at would be the Agents that are triggered when an Order Release is created (agents that listen to the event Order Release - Created). You should really only have one agent listening to this event. If you have two, I would look at consolidating them, or triggering one from the other.

Let me know what you find.

Regards,

James Foran
Toll Solutions
TOLL Group - Logistics and Transport in Australia, Australias Largest Logistics and Transport Provider
Reply With Quote