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 721854, 1 year ago
Unable to resolve ("ejb name")
via Oracle Community by adrina, 2 years ago
Unable to resolve 'triviMailSession'. Resolved ''; remaining name 'triviMailSession'
via Oracle Community by jack_van_ooststroom, 2 years ago
Unable to resolve 'test'. Resolved ''; remaining name 'test'
via Oracle Community by 653189, 2 years ago
Unable to resolve 'ivtQCF' Resolved ; remaining name 'ivtQCF'
via Oracle Community by 871935, 2 years ago
While trying to lookup 'SOAServiceInvokerBean#oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean' didn't find subcontext 'SOAServiceInvokerBean#oracle'. Resolved ''; remaining name 'SOAServiceInvokerBean#oracle/integration/platform/blocks/sdox/ejb/api/SOAServiceInvokerBean'
via Oracle Community by 871667, 1 year ago
While trying to lookup 'mdb01.queue01' didn't find subcontext 'mdb01'. Resolved ''; remaining name 'mdb01/queue01'
javax.naming.NameNotFoundException: Unable to resolve ("ejb name") at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:924) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:230) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:154) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:258) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:363) at javax.naming.InitialContext.lookup(InitialContext.java:347)