Starting Workflow Services Fails With Error oracle.apps.fnd.cp.gsc.SvcComponentContainerException Could not start Service Component Container
(Doc ID 1663093.1)
Last updated on AUGUST 23, 2023
Applies to:
Oracle Workflow - Version 12.2.2 to 12.2.8 [Release 12.2]Information in this document applies to any platform.
Symptoms
On a 12.2.3 instance, the Workflow services are not starting, and following error is shown in log files:
LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.startLogger() : BEGIN [default implementation]
Could not start Service Component Container -> oracle.apps.fnd.cp.gsc.SvcComponentContainerException: BES system could not establish connection to the control queue after 180 seconds
oracle.apps.fnd.cp.gsc.SvcComponentContainerException: BES system could not establish connection to the control queue after 180 seconds
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.startBusinessEventListener(SvcComponentContainer.java:1601)
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.start(SvcComponentContainer.java:855)
at oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer.main(GSMSvcComponentContainer.java:424)
Could not start Service Component Container -> oracle.apps.fnd.cp.gsc.SvcComponentContainerException: BES system could not establish connection to the control queue after 180 seconds
oracle.apps.fnd.cp.gsc.SvcComponentContainerException: BES system could not establish connection to the control queue after 180 seconds
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.startBusinessEventListener(SvcComponentContainer.java:1601)
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.start(SvcComponentContainer.java:855)
at oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer.main(GSMSvcComponentContainer.java:424)
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 |