E1: ORCH: Concurrent Processing of Groovy Scripts is Resetting a For Loop's Index Incorrectly
(Doc ID 2933117.1)
Last updated on MARCH 07, 2023
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 to 9.2 [Release 9.2]JD Edwards EnterpriseOne Tools - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.
Symptoms
If there are multiple groovy scripts using the same iteration index variable for the FOR loop (eg: "i" as the index variable), it is observed that the value for the index variable is getting reset incorrectly when such orchestrations are executed concurrently. This can be noticed by adding "write warnings" to the log recording the array size and the index variable value.
For example, both ORCH A and ORCH B shall contain some groovy steps using the same index variable "i" for the FOR loop. When ORCH B is called while ORCH A is executing, ORCH B interrupts ORCH A and reset the value of 'i' inside ORCH A's processing.
This issue can happen in other scripting languages like jruby and jython as well, not just with groovy.
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 |
| Cause |
| Solution |
| References |