E1: ORCH: Report Step Does Not Fail When UBE Is Not Complete After UBEMaxSynchronousWaitTime (After "not complete within Max Wait Time setting" Appears in AIS Server Log)
(Doc ID 2920340.1)
Last updated on MARCH 01, 2023
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After a synchronous UBE request, the rest of the orchestration starts after UBEMaxSynchronousWaitTime has passed and runs for awhile, until the "not complete within Max Wait Time setting" warning appears in the log. When the warning appears, the orchestration stops.
Changes
Steps to reproduce:
1. Run orchestration that runs report that takes longer than UBEMaxSynchronousWaitTime (without fire and forget turned on)
2. Perform some steps in orchestration after this. Note that this part of the orchestration runs for awhile after UBEMaxSynchronousWaitTime has passed (until the "until the "not complete within Max Wait Time setting" warning appears in the log).
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |