Last updated on NOVEMBER 05, 2016
Applies to:
Oracle WebLogic Server - Version 12.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
Cannot deploy EJB based application (Maven generated) to WLS 12.1.1 due to the error below.
No problem with WLS 10.3.5/6.
Error
weblogic.application.naming.ReferenceResolutionException: [J2EE:160199]Error resolving ejb-ref "myPkg.myAdminServlet/clusterConfigFacade" from module "myWebClient.war" of application "myAppli". The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because multiple EJBs in the application were found to implement the "myPkg.myAttributeFacade" interface, including myFacade.jar/myAttributeFacadeBean, myWebClient.war/myAttributeFacadeBean. Specify a qualified ejb-link for this ejb-ref to indicate which EJB is the target of this ejb-ref.
at weblogic.application.naming.EnvUtils.findInfo(EnvUtils.java:856)
at weblogic.application.naming.EnvUtils.findInfoByReferenceClass(EnvUtils.java:783)
at weblogic.application.naming.EjbReferenceResolver.resolveEjbRef(EjbReferenceResolver.java:92)
at weblogic.application.naming.EjbReferenceResolver.resolve(EjbReferenceResolver.java:71)
at weblogic.application.naming.EjbReferenceResolver.get(EjbReferenceResolver.java:58)
at weblogic.application.naming.EnvironmentBuilder.bindEJBReferences(EnvironmentBuilder.java:1226)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:267)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:2730)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1691)
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms