CCB V2.2.0 Foreign Key Reference Error Occurs when Calling RegisterCharacteristic Change Handler

(Doc ID 799278.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Utilities Customer Care and Billing - Version: 2.2.0 and later   [Release: 2.2 and later ]
Information in this document applies to any platform.

Symptoms

When the RegisterCharacteristic Change Handler is called during the addition of a Characteristic, the following errors occur:




Log file
 -  11:07:23,680 [JVM 1 Ping] ERROR (cobol.host.OptimizedRemoteExecuterStub) An exception occurred invoking remote command.
 -  11:07:23,680 [JVM 1 Ping] INFO  (cobol.host.RemoteJVMConnectionImpl) Connection to JVM 1 being shunned
 -  11:07:23,680 [JVM 1 Ping] ERROR (cobol.host.RemoteJVMConnectionImpl) An exception has occurred calling the remote JVM
 -  11:07:23,758 [JVM 2 Ping] ERROR (cobol.host.OptimizedRemoteExecuterStub) An exception occurred invoking remote command.
 -  11:07:23,789 [JVM 1 Ping] ERROR (cobol.host.RemoteJVMConnectionImpl) Error encountered while pinging child JVM #1.  Will 'shun' that JVM.
com.splwg.base.support.cobol.host.InputClosedException:
The following stacked messages were reported as the LoggedException was rethrown:
com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:76): An exception has occurred calling the remote JVM
com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:76): An exception occurred invoking remote command.

The root LoggedException was: The input was closed.
    at com.splwg.base.support.cobol.host.OptimizedObjectEncoder.readOptimized(OptimizedObjectEncoder.java:176)
    at com.splwg.base.support.cobol.host.OptimizedDataInput.readOptimized(OptimizedDataInput.java:41)
    at com.splwg.base.support.cobol.host.OptimizedObjectEncoder.readSerializable(OptimizedObjectEncoder.java:245)
    at com.splwg.base.support.cobol.host.OptimizedDataInput.readSerializable(OptimizedDataInput.java:49)
    at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.sendRequestGetResponse(OptimizedRemoteExecuterStub.java:76)
    at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:52)
    at com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:89)
    at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl$PingChildRunnable.performPingLoop(RemoteJVMConnectionImpl.java:283)
    at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl$PingChildRunnable.run(RemoteJVMConnectionImpl.java:271)
    at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.EOFException
    at java.io.DataInputStream.readByte(DataInputStream.java:243)
    at com.splwg.base.support.cobol.host.OptimizedObjectEncoder.readOptimized(OptimizedObjectEncoder.java:75)
    ... 9 more


This error will still occur when only method stubs exist within the Change Handler - custom code within these methods is not required to trigger the error.

The characteristic type being added is of type Adhoc, and an adhoc value is provided.

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