Clustered EJB 2.X in WebLogic 12.2.1.3 Throws RemoteEJBInvokeException When Accessed Using wlclient.jar
(Doc ID 2660233.1)
Last updated on AUGUST 18, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.3.0 to 14.1.1 [Release 12c]Information in this document applies to any platform.
Symptoms
A standalone EJB client receives weblogic.rmi.RemoteEJBInvokeException instead of custom application exception when accesses an EJB 2.x deployed on a cluster in WebLogic 12.2.1.3.0.
Use Case
1. Deploy an EJB 2.x application, with a custom application exception, on a cluster in WebLogic 12.2.1.3.0.
2. Access the EJB using a standalone EJB client using wlclient.jar.
3. The standalone EJB client receives weblogic.rmi.RemoteEJBInvokeException when the custom application exception is thrown.
4. Expectation is that the standalone EJB client should receive the custom application exception however the custom application exception is wrapped inside weblogic.rmi.RemoteEJBInvokeException.
5. If the standalone EJB client uses wlthint3client.jar instead of wlclient.jar then it recives the custom application exception.
Changes
Upgrade WebLogic from 12.1.3.0 to 12.2.1.3.0
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 |