Global Transaction Timeout Is Exceeded Even If TIMEOUT Property Is Used Because of "Bad expiration date format"
(Doc ID 1349775.1)
Last updated on NOVEMBER 01, 2019
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
You have developed a SOA Composite Application and have successfully deployed this to Oracle Fusion Middleware 11g Release 1.
Within the implementation of your composite you have an activity such as an INVOKE to a JCA Adapter (for example, a call to a database stored procedure through the Database Adapter) or a correlated RECEIVE, such that the INVOKE or RECEIVE activity can take an arbitrary amount of time during the current transaction.
Since the time at which the activity can receive it's expected response lies outside of the control of the process, you are utilizing an appropriate TIMEOUT property to prevent the process from exceeding the Global Transaction Timeout, which you are setting dynamically. However at runtime you encounter encounter the following exception, possibly intermittently:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document