My Oracle Support Banner

Outgoing CCR Is Not Generated If IMOCF Destination-host Doesn't Match Route Server Name (Doc ID 1497576.1)

Last updated on AUGUST 02, 2018

Applies to:

Oracle Communications Service Broker - Version 5.0.0.2 and later
Information in this document applies to any platform.

Symptoms

Outgoing CCR (Credit Control Request) is not generated if IMOCF destination-host doesn't match route server name.

The configuration caused OCSB not to send CCR to destination server/peer with different name from name defined in IMOCF Ro destination-host-AVP.
When the Diameter Route and Peer using Server/Hosts name different from IMOCF destination-host AVP the SSU cannot generate CCR toward this destination even when available and answered on DWR. Following ERROR and exception occurred in the SSU Log:

2012-03-18 17:09:05,751 ERROR [ACTIVE] ExecuteThread: '97' for queue: 'weblogic.kernel.Default (self-tuning)' AbstractProtocolAdapterApplication - unable to send request ...dropping event
java.io.IOException: Unable to send request (no available peers)
  at com.bea.wcp.diameter.Transaction.start(Unknown Source)
  at com.bea.wcp.diameter.Request.commit(Unknown Source)
  at com.bea.wcp.diameter.Session.sndMessage(Unknown Source)
  at com.bea.wcp.diameter.Request.send(Unknown Source)
  at com.bea.wcp.diameter.Request.send(Unknown Source)
  at oracle.axia.protocol.diameter.impl.AbstractProtocolAdapterApplication.sendDiamMsg(AbstractProtocolAdapterApplication.java:272)
  at oracle.axia.protocol.diameter.impl.AbstractProtocolAdapterApplication.sendDiamReq(AbstractProtocolAdapterApplication.java:256)
  at oracle.axia.protocol.diameter.impl.UniversalProtocolAdapterApplication.handleOutboundRequest(UniversalProtocolAdapterApplication.java:183)
  at oracle.axia.protocol.diameter.impl.AbstractProtocolAdapterApplication$1.onEvent(AbstractProtocolAdapterApplication.java:115)
  at oracle.axia.protocol.diameter.impl.AbstractProtocolAdapterApplication$1.onEvent(AbstractProtocolAdapterApplication.java:105)
  at oracle.axia.protocol.impl.StatsAccumulatingProtocolAdapterEventBroker$1.onEvent(StatsAccumulatingProtocolAdapterEventBroker.java:45)
  at oracle.axia.protocol.impl.StatsAccumulatingProtocolAdapterEventBroker$1.onEvent(StatsAccumulatingProtocolAdapterEventBroker.java:41)
  at oracle.axia.api.eventbroker.DefaultScheduler$EventWork.run(DefaultScheduler.java:148)
  at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
  at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:524)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.