Database Reference
In-Depth Information
Configuring BPEL timeouts
Receiving connection timeout-related errors is a common scenario for processing
large payload or a large number of message files.
Some of the scenarios that require value changes in the
Timeout
parameter are lis-
ted as follows:
• One needs more than 30 seconds for running the composite application
with a large payload
• Application logfiles or EM console has timeout errors
There are multiple solutions available to resolve timeout-related errors. The following
timeout controls are available in BPEL Process Manager:
• JTA Transaction Timeout aka Global Transaction Timeout
• BPEL EJB's Transaction Timeout
•
syncMaxWaitTime
• Transaction setting in
composite.xml
Global Transaction Timeout parameter setting is at the WebLogic container level.
Please note that the BPEL Process Manager programs run within the WebLogic plat-
form. The Global Transaction Timeout parameter should be higher than any BPEL
program's timeout settings.
It is required to set the timeout values as follows:
Global Transaction Timeout ≥ BPEL EJB's
Transaction Timeout ≥ syncMaxWaitTime
Setting the JTA Transaction Timeout aka Global
Transaction Timeout parameters
The Global Transaction Timeout value is set at the WebLogic domain level. This prop-
erty controls the transaction timeout seconds for active transactions. If the transaction
is still in the "active" state after this time, it is automatically rolled back.
