Pipeline Can Not Be Stopped Gracefully When Http/SNMP Monitoring Is Activated. (Doc ID 557263.1)

Last updated on JULY 18, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.3.0.0.0 version, it is observed that pipeline can not be stopped gracefully when HTTP/SNMP monitoring is activated.

BRM documentation has been updated recently with following statement:

"Important. If you use HTTP or SNMP monitoring in a Pipeline Manager instance, you need to stop all monitoring requests to Pipeline Manager before you stop the Pipeline itself. To stop the monitoring  requests, stop the master SNMP agent. You can use the kill command, for example: kill -9 master_agent_pid "

This is not an acceptable workaround for the reason it is not compatible with SNMP architecture. Indeed the master_agent can be used to monitor several pipelines. As a result it is not acceptable to stop it when you only want to stop one pipeline.

STEPS:

The issue can be reproduced at will with the following steps:
1. Start Master Agent
2. Activate OMF on pipeline

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