Unable to Start Workflow Services after Patching - Error in log file: "Missing initialization parameters, unable to initialize service."

(Doc ID 1638213.1)

Last updated on AUGUST 08, 2016

Applies to:

Oracle Workflow - Version 11.5.10.2 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Workflow Mailer

Error in Workflow Mailer Services when trying to start after patch 17754952:R12.BOM.C is applied.

The issue can be reproduced at will with the following steps:
Start Workflow Services in OAM and all the services start successfully.

Below is a list of errors you can find in different log files:

ERRORS
-----------
DEBUG SERVICE log file shows:
[3/7/14 10:05:48 AM] [main] Starting GSF service with concurrent process id = 2990024.
[3/7/14 10:05:48 AM] [main] Initialization Parameters: XYZ
[3/7/14 10:05:48 AM] [EXCEPTION] [main] java.util.NoSuchElementException

........
[3/7/14 10:05:48 AM] [ERROR] [main] Missing initialization parameters, unable to initialize service.


SFM Controller Service log file shows:

[3/7/14 10:06:14 AM] [main] Starting GSF service with concurrent process id = 2990026.
[3/7/14 10:06:14 AM] [main] Initialization Parameters: SM_MSG_WAIT_TIME:19:SM_SLEEP_TIME:1:XDP_CTRL_WAIT_TO_KILL_MINUTES:2:
[3/7/14 10:06:14 AM] [EXCEPTION] [main] java.lang.NumberFormatException: For input string: "SM_SLEEP_TIME"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)

...........
[3/7/14 10:06:14 AM] [ERROR] [main] Missing initialization parameters, unable to initialize service.


Workflow Agent Listener Service log file shows:

[3/7/14 10:02:19 AM] [main] Starting GSF service with concurrent process id = 2990015.
[3/7/14 10:02:19 AM] [main] Initialization Parameters: SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=4:SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:SVC_COMP_MAX_ERROR_COUNT=10
[3/7/14 10:02:19 AM] [EXCEPTION] [main] java.lang.NumberFormatException: For input string: "SVC_CONTAINER_LOOP_SLEEP=10"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

.........
[3/7/14 10:02:19 AM] [ERROR] [main] Missing initialization parameters, unable to initialize service.

Workflow Document Web Services Service log file shows:

[3/7/14 10:06:43 AM] [main] Starting GSF service with concurrent process id = 2990025.
[3/7/14 10:06:43 AM] [main] Initialization Parameters: SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=5:SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:SVC_COMP_MAX_ERROR_COUNT=5
[3/7/14 10:06:43 AM] [EXCEPTION] [main] java.lang.NumberFormatException: For input string: "SVC_CONTAINER_LOOP_SLEEP=10"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

..........
[3/7/14 10:06:43 AM] [ERROR] [main] Missing initialization parameters, unable to initialize service.


Workflow Mailer Service log file shows:

[3/7/14 10:04:09 AM] [main] Starting GSF service with concurrent process id = 2990020.
[3/7/14 10:04:09 AM] [main] Initialization Parameters: SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=4:SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:SVC_COMP_MAX_ERROR_COUNT=10:SVC_PROXY_SET=NONE:SVC_PROXY_HOST=NONE:SVC_PROXY_PORT=NONE
[3/7/14 10:04:09 AM] [EXCEPTION] [main] java.lang.NumberFormatException: For input string: "SVC_CONTAINER_LOOP_SLEEP=10"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

........
[3/7/14 10:04:09 AM] [ERROR] [main] Missing initialization parameters, unable to initialize service.


BUSINESS IMPACT
------------------------------
No workflow processing is happening on the entire Ebiz causing all business functions that depend on Workflow to be stalled.

Changes

Applied patch 17754952:R12.BOM.C - Cost Management Operating Unit ID source validation correction.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms