BatchController Becomes Unusable Once CM Restarted (Doc ID 987593.1)

Last updated on DECEMBER 23, 2014

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Information in this document applies to any platform.

Goal

Batch controller becomes unusable once the CM is restarted.It is not able to automatically establish connection with the newly started CM so batch controller also requires a restart if CM is restarted.

Steps to Reproduce
1. Start CM
2. Start Batch controller
3. Stop CM
4. Start CM

Error messages in cm.pinlog:

Solution

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