Last updated on OCTOBER 18, 2016
Applies to:Oracle Utilities Customer Care and Billing - Version 18.104.22.168.0 and later
Oracle Utilities Framework - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms