SOA log showing timeouts when a large schedule is submitted (Doc ID 1490244.1)

Last updated on SEPTEMBER 07, 2016

Applies to:

Hyperion Financial Close Management - Version 11.1.2.1.000 to 11.1.2.4.103 [Release 11.1]
Information in this document applies to any platform.

Symptoms

When attempting to open a large schedule in excess of 1800 tasks, the following error occurs in the SOA log:

[2012-08-08T14:27:10.274-05:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-4] [userId: QAtest3] [ecid: 0000J^7fOSBD4i5pzO^AyW1G8Keo0001LG,0:1:100003863] [APP: soa-infra] failed to handle message[[
weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
BEA1-124176D3EBD774FB4ACE
...
[2012-08-08T14:27:10.275-05:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-4] [userId: QAtest3] [ecid: 0000J^7fOSBD4i5pzO^AyW1G8Keo0001LG,0:1:100003863] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
BEA1-124176D3EBD774FB4ACE
...
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
BEA1-124176D3EBD774FB4ACE
...
BEA1-124176D3EBD774FB4ACE
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

Changes

 Additional tasks being added to a schedule or a new schedule being submitted with a large number of tasks (in this case an excess of 1800).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms