Pipeline Can Not Be Stopped Gracefully When Http/SNMP Monitoring Is Activated.
Last updated on JULY 18, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 18.104.22.168.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:
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.
The issue can be reproduced at will with the following steps:
1. Start Master Agent
2. Activate OMF on pipeline
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