My Oracle Support Banner

Error of collection cancellation associated with debt class with plug-in script (Doc ID 1957189.1)

Last updated on JUNE 14, 2021

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.4.0.2.0 and later
Information in this document applies to any platform.

Symptoms

<Steps to Reproduce>
(1) On an Account, create a collection process.
(2) Create an active SA for the collection process.
(3) Go to SA type of the created SA and check debt class.
(4) Create a plugin-in script (even no any steps).
(5) Create an Algorithm Type with the plug-in script. Choose Algorithm Entity as "Debt Class - Collection Process Cancellation".
(6) Create an Algorithm with Algorithm Type created in step 5.
(7) Go to the debt class in step 3.
(8) On System Event "Collection Proc Cancellation Rule", change Algorithm to the one created in step 6.
(9) Try to Open the collection process created in step 1.

<Actual Result>
A popup error message , "System error, Please see logs for more detail".

In debug log, there are such error messages,

SYSUSER - 922621-20123-1 2014-11-10 08:57:53,977 [Parent Reader:Thread-55] ERROR (support.cobol.CobolToJavaGateway) A system error occurred calling method invoke on class com.splwg.ccb.domain.admin.cobolInterface.debtClass.DebtClassCollectionProcessAlgorithmFromCobolWrapper_Impl
com.splwg.shared.common.LoggedException: Error invoking method invoke
at com.splwg.shared.common.LoggedException.wrap(LoggedException.java:199)
at com.splwg.shared.common.LoggedException.wrap(LoggedException.java:87)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.dispatchToRequestedMethod(CobolToJavaGateway.java:380)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.access$300(CobolToJavaGateway.java:274)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.dispatchToRequestedMethod(CobolToJavaGateway.java:269)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.access$000(CobolToJavaGateway.java:251)
at com.splwg.base.support.cobol.CobolToJavaGateway.callJava(CobolToJavaGateway.java:73)
at com.splwg.base.support.cobol.host.command.CobolToJavaGatewayCommand.invoke(CobolToJavaGatewayCommand.java:33)
at com.splwg.base.support.cobol.host.PerformCommandExecuter.invoke(PerformCommandExecuter.java:68)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterSkel$RequestSocketReader.readRequestExecuteAndRespond(OptimizedRemoteExecuterSkel.java:167)
at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterSkel$RequestSocketReader.run(OptimizedRemoteExecuterSkel.java:101)
at com.splwg.base.support.cobol.host.SocketThreadPool$WrappingParentRunnable.run(SocketThreadPool.java:204)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at com.splwg.ccb.domain.admin.cobolInterface.debtClass.DebtClassCollectionProcessAlgorithmFromCobolWrapper_Impl.mapResultToCOBOL(DebtClassCollectionProcessAlgorithmFromCobolWrapper_Impl.java:61)
at com.splwg.ccb.domain.admin.cobolInterface.debtClass.DebtClassCollectionProcessAlgorithmFromCobolWrapper_Gen.mapResultToCOBOL(DebtClassCollectionProcessAlgorithmFromCobolWrapper_Gen.java:88)
at com.splwg.base.support.algorithm.AbstractFromCobolAlgorithmWrapper.invoke(AbstractFromCobolAlgorithmWrapper.java:53)
at com.splwg.ccb.domain.admin.cobolInterface.debtClass.DebtClassCollectionProcessAlgorithmFromCobolWrapper_Gen.invoke(DebtClassCollectionProcessAlgorithmFromCobolWrapper_Gen.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.dispatchToRequestedMethod(CobolToJavaGateway.java:356)
... 11 more


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


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