AIA 2.5 Comms And Customer Hub PIPs--new CPARTY_SYNC_TOPIC Subscriber Created With Every Restart

(Doc ID 1498120.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Communications Integration Pack for Agent Assisted Billing Care - Version 2.5 and later
Information in this document applies to any platform.


On : 2.5 version, AIA Comm PI for Billing Mgmnt 

Every time we restart either the Comms or the Customer Hub PIP, a new subscriber is created for the CPARTY_SYNC_TOPIC AQ JMS topic. I believe the subscriber is created for the SyncCustomerPartyListBRM_01CommsJMSConsumer ESB process.
Two problems result:
1. The number of messages in the CPARTY_SYNC_TOPIC_TABLE is always growing, I believe because messages are saved for subscribers that will never return. This imposes a significant maintenance burden.

2. The max number of subscribers is finite, so that eventually we run into these exceptions when we restart:

<2011-04-06 10:01:22,151> <WARN> <default.collaxa.cube.activation> <JMSAdapter::Inbound>
Error while creating Topic consumer:.
Please examine the log file to determine the problem.
Caused by: oracle.jms.AQjmsException: ORA-24067: exceeded maximum number of subscribers for queue JMSUSER.CPARTY_SYNC_TOPIC
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 5682
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1

at oracle.jms.AQjmsSession.addDurableSubscriber(
at oracle.jms.AQjmsSession.createSubInOldMode(
at oracle.jms.AQjmsSession.createDurableSubscriber(
at oracle.jms.AQjmsSession.forceCreateOldSubscriber(
at oracle.jms.AQjmsSession.createSubscriber(
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnect


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