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 843830, 2 years ago
While trying to lookup 'example.ejb.session.Hello' didn't find subcontext 'example'. Resolved ''; remaining name 'example/ejb/session/Hello'
via Oracle Community by user8680179, 1 year ago
While trying to lookup 'example.ejb.session.Hello' didn't find subcontext 'example'. Resolved ''; remaining name 'example/ejb/session/Hello'
via coderanch.com by Unknown author, 2 years ago
While trying to lookup 'example.ejb.session.Hello' didn't find subcontext 'example'. Resolved ''; remaining name 'example/ejb/session/Hello'
via Oracle Community by 666705, 2 years ago
Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
javax.naming.NameNotFoundException: While trying to lookup 'example.ejb.session.Hello' didn't find subcontext 'example'. Resolved ''; remaining name 'example/ejb/session/Hello' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)