My Oracle Support Banner

Failed READ Due To EJBException While Accessing Oracle Revenue Management and Billing (ORMB) Application Installed in Native Mode (Doc ID 2390587.1)

Last updated on SEPTEMBER 04, 2024

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.4.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On ORMB v2.4.0.1.0 against FW v4.2.0.3, Error Failed READ due to EJBException comes up when trying to access the ORMB application.

Native installation was suggested as a work around for same error, but even after following the native mode installation, we are still facing the same error.

Below is the error from the spl_web.log:

[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default
(self-tuning)'] ERROR (splwg.serviceclient.RemotePageServiceDispatcherHelper) Failed READ due to EJBException
javax.ejb.EJBException: EJB Exception: ; nested exception is:
com.oracle.pitchfork.interfaces.LifecycleCallbackException: Failure to invoke protected void com.splwg.ejb.service.impl.ServiceBean.initializeContext() on
bean class class com.splwg.ejb.service.impl.SPLServiceBean_8o7vtd_Impl with args: null at
weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:117)
Caused by: com.oracle.pitchfork.interfaces.LifecycleCallbackException:
Failure to invoke protected void
com.splwg.ejb.service.impl.ServiceBean.initializeContext()
...
Caused by: java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.splwg.ejb.service.impl.ServiceBeanContext
...

Below is the error from the spl_service.log:

WARN (host.sockets.UnixDomainSocket) Exception in static initializer loading
library:com_splwg_base_support_cobol_host_sockets_UnixDomainSocketNative java.lang.UnsatisfiedLinkError: no
com_splwg_base_support_cobol_host_sockets_UnixDomainSocketNative in java.library.path
Failed READ due to EJBException

Note that the login after immediate installation works successfully in embedded mode, but conversion to native mode fails to get the application up and running as well.

Changes

 

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
Changes
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.