My Oracle Support Banner

How to start Threadpoolworkers (Doc ID 1929234.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.4.0.1.0 and later
Oracle Utilities Framework - Version 4.2.0.1.0 and later
Information in this document applies to any platform.

Goal

**Disclaimer:** This KM article may include the following abbreviations:

CCB - Oracle Utilities Customer Care and Billing
OUAF/FW - Oracle Utilities Framework
RMI - Remote Method Invocation
JMX - Java Management Extensions
PID - Process ID
TPW - Threadpoolworker

 

spl.sh script appears to have incorrect RUNOPTS. current: DEFAULT_RUNOPTS=”-d Y DEFAULT=5” expected: DEFAULT_RUNOPTS=”-d Y –p DEFAULT=5”
When the correct RUNOPTS are configured then the threadpoolworker_user_exit appears to be ignored. If you start a second TPW pool (e.g. POOLA) there is no way to manage it independent of the first TPW pool (e.g. DEFAULT).

jmxbatchclient appears to be ignorant of the PID associated with additional TPWs. jmxbatchclient does not provide any management (e.g. stopNode) of the additional TPW (e.g. POOLA). The stopNode appears to only manage the initial TPW (e.g. DEFAULT).
 

Solution

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
Goal
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.