My Oracle Support Banner

Exception is Wrapped as RemoteEJBInvocation After Upgrading to WebLogic (Doc ID 2762529.1)

Last updated on MARCH 26, 2021

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


After upgrading WebLogic from WLS 10.3.6 to Weblogic,  exception isn't wrapped correctly when client application makes a call to EJB.  And many errors thrown from EJB's are wrapped as RemoteEJBInvocation Exception.  This behavior happened only when deploying application on a multi node cluster.  And same behavior doesn't occurred when deploying application on stand alone server.

Scenario 1: Client -> EJB 1 -> EJB 2

Application scenario is to have 2 EJB's: EJB1 and EJB2. Java client application will invoke a function/method defined in EJB1. The method in EJB1 will in turn make a call to a function in EJB2. When an exception is thrown from EJB2, the exception is wrapped as RemoteEJBInvocation Exception.

Scenario 2: Client -> EJB 1

The exception occurs even accessing a single EJB. When a custom exception is thrown from EJB1 to a remote java class, the exception is wrapped as RemoteEJBInvocation.



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

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