OPP And Workflow Related Concurrent Manager Actual And Target Process Are Not In Sync Caused by: Java.lang.RuntimeException: Java.lang.IllegalArgumentException: Null Username
(Doc ID 2767944.1)
Last updated on MAY 11, 2021
Applies to:Oracle Concurrent Processing - Version 12.2.6 to 12.2.6 [Release 12.2]
Information in this document applies to any platform.
After concurrent manager restart some concurrent managers like Output Post Processor, Workflow Agent Listener Service ,Workflow Mailer Service and Workflow Document Web Services Service actual process and target process were not in sync.
Below exception seen in manager log.
Unable to initialize state monitor.
oracle.apps.fnd.common.AppsException: oracle.apps.fnd.common.PoolException: Exception creating new Poolable object.
Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException: Null Username
The issue can be reproduced at will with the following steps:
1.Clone a instance from another EBS instance
2.Start Concurrent manager.
3.Verify actual and target process of concurrent managers in Administer concurrent Managers form.
Cloned instance from Production
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