SIGUSR1 Trigger Reports Wrong Count of CMs
Last updated on FEBRUARY 13, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, CM
- In a AIA-BRM setup, there were connectivity issues wherein JCA adapter would throw "ErrMsg=ERR_STREAM_IO" error.
- On analysis, it was observed that number of CMs configured in CM pin conf (max 50) were being reached, see below message in cm pinlog:
- This behavior of wrong calculation of CMs was especially occurring during daily billing or syncpdc execution.
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