OCSB PN Failure During Revive Of The IMOCF Module (Doc ID 1399874.1)

Last updated on JULY 30, 2017

Applies to:

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

Symptoms

There is failure of OCSB PN during revive of the IMOCF module.
On IMOCF over IMSCF in a split domain system with 2 SSU and 2 PN, during the restart of the second PN, an exception is thrown related to the revive of IMOCF module.

This exception can be found in the server log:

2011-08-29 04:09:45,190 ERROR ActorDistributedCacheWorker:4 ScheduledActorAction - Actor (Binary(length=16, value=0x000000034E5B64900000000000000006), class: com.convergin.specific.axia.framework.mediation.impl.SessionActor) action threw RuntimeException during oracle.axia.actor.scheduling.ActorReviveAction transaction. Next action: oracle.axia.actor.scheduling.ActorSuspendAction java.lang.RuntimeException: failed deserializing object, cause: com.convergin.imocf.common.overImscf.ImocfOverImscfStateMachine;
com.convergin.imocf.common.overImscf.ImocfOverImscfStateMachine; no valid constructor
at com.convergin.specific.osgi.framework.services.impl.serialization.OsgiSerializer.deserializeObject(OsgiSerializer.java:71)
at
com.convergin.common.framework.engine.impl.SessionImpl.revive(SessionImpl.java :190)

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