My Oracle Support Banner

Workflow Inbound Notifications Agent Listener Fails to Start with Error 'Could not start component' And 'Outbound thread count must be 0. It is currently set to 1' (Doc ID 2905263.1)

Last updated on OCTOBER 31, 2022

Applies to:

Oracle Workflow - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Unable to start "Workflow Inbound Notifications Agent Listener" due to below error.

Due to this, notifications are not getting processed from IMAP -> Inbox folder.


ERROR
-----------------------
oracle.apps.fnd.cp.gsc.SvcComponentContainerException: Could not start component; performing rollback -> oracle.apps.fnd.cp.gsc.SvcComponentException: Validation failed for the following parameters -> {PROCESSOR_OUT_THREAD_COUNT=Outbound thread count must be 0. It is currently set to 1}. Parameters were -> {PROCESSOR_OUT_THREAD_COUNT=1, PROCESSOR_ERROR_LOOP_SLEEP=60, LISTENER_PROCESS_EVT_COUNT=500, PROCESSOR_IN_THREAD_COUNT=1, PROCESSOR_LOOP_SLEEP=120, PROCESSOR_MAX_ERROR_COUNT=10, PROCESSOR_MAX_LOOP_SLEEP=0, COMPONENT_LOG_LEVEL=5, NAVIGATION_RESET_THRESHOLD=0, PROCESSOR_READ_TIMEOUT_CLOSE=Y, PROCESSOR_READ_TIMEOUT=0, SQL_TRACE_LEVEL=-1}
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.handleComponentEvent(SvcComponentContainer.java:2232)
at oracle.apps.fnd.cp.gsc.SvcComponentContainer.onBusinessEvent(SvcComponentContainer.java:301)
at oracle.apps.fnd.wf.bes.DispatchThread.run(Unknown Source)

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.