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 user597820, 1 year ago
While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved '']; remaining name 'jms/testConnectionFactory'
via Oracle Community by user7574630, 1 year ago
Unable to resolve 'AccountManager'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'AccountManager'. Resolved '']; remaining name 'AccountManager'
via Oracle Community by 692827, 2 years ago
While trying to lookup 'p13n.leasemanager' didn't find subcontext 'p13n'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'p13n.leasemanager' didn't find subcontext 'p13n'. Resolved '']; remaining name 'p13n/leasemanager'
javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved '']; remaining name 'jms/testConnectionFactory' at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259) at weblogic.jndi.internal.ServerNamingNode_1036_WLStub.lookup(Unknown Source) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:424) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412) at javax.naming.InitialContext.lookup(InitialContext.java:411)