Actions Performed by Users Recieve a "timed out waiting for" Error When This Action Also Triggers an Agent to Execute
Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 6.1 to 6.1.1 - Release: 6.1 to 6.1
Information in this document applies to any platform.
An Agent is configured that is triggered from an action performed by the User. When this user performs this action (and therefore triggering the configured agent), they eventually receive a time out message similar to the following:
2010-03-23 11:37:31.484 651147 Error Exception SECURE RESOURCES timed out waiting for SHIPMENT: DOMAIN.SHIPMENT_ID. The object is held by Activity: <AGENT_ACTION> (AGENT), Machine: DEFAULT, Thread: agentUtility - 1, Process: 651115, Since: 2010-03-23 11:36:31 America/Los_Angeles.
The above error uses an example as follows. However, this problem can occur when any user action is triggering an agent to execute.
Example: A Shipment Agent is configured and triggered when a shipment is tendered (Action -> Secure Resources). When a Shipment is tendered and therefore this agent is triggered, the Secure Resources action is timing out with the following:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms