Recently I faced issue while deploying existing custom ear, while deploying on upgraded WebLogic Version 12C. The existing ear is previously compatible with older WebLogic version 10.3.4
While deploying same ear on newer version of WebLogic got following error on server and console -
Solution:
To deploy it, I have removed my EJB module jar from
XXX.ear
|__ xxx.war
|__ WEB-INF
|__ lib
|__ ejb jar [which causing issue]
Note, in my case the jar I removed from WAR file, is already present under EAR, and having duplicate occurrence inside the WAR/lib.
Hope this will help.
While deploying same ear on newer version of WebLogic got following error on server and console -
weblogic.management.DeploymentException:
weblogic.application.naming.ReferenceResolutionException: [J2EE:160199]Error resolving
ejb-ref "com.xxx.xxx.xxx.xxx.xxx.xxx.XXXX/xxxRemote"
from module
"XXX-X.X.X.war"
of application "XXX-X.X.X". The ejb-ref does not
have an ejb-link and the JNDI name of the target Bean has not been specified.Solution:
To deploy it, I have removed my EJB module jar from
XXX.ear
|__ xxx.war
|__ WEB-INF
|__ lib
|__ ejb jar [which causing issue]
Note, in my case the jar I removed from WAR file, is already present under EAR, and having duplicate occurrence inside the WAR/lib.
Hope this will help.
No comments:
Post a Comment