weblogic.management.DeploymentException: Could not deploy: 'cp2.jar': JNDI name in use

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
Could not deploy: 'cp2.jar': JNDI name in use
via Oracle Community by 3004, 1 year ago
Could not deploy: 'HelloWorld_EJB.jar': JNDI name in use
via Oracle Community by 3004, 1 year ago
Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
via Oracle Community by 3004, 1 year ago
Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
via Google Groups by minjiang, 3 months ago
Could not deploy: 'kbf.jar' Possible reasons include: 1. The bean or an interface class has been modified but the deployment descriptor has not been updated 2. The database mappings in the deployment descriptor do not match the database definition 3. The jar file is not a valid jar file 4. The jar file does not contain a valid bean
via Google Groups by Surya, 3 months ago
Could not deploy: 'ejb_basic_containerM anaged.jar' Possible reasons include: 1. The bean or an interface class has been modified but the deployment descriptor has not been updated 2. The database mappings in the deployment descriptor do not match the database definition 3. The jar file is not a valid jar file 4. The jar file does not contain a valid bean
weblogic.management.DeploymentException: Could not deploy: 'cp2.jar': JNDI name in use
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
at weblogic.j2ee.Application.deploy(Application.java:167)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:217)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:187)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1136)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:773)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:750)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:256)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:1075)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.