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 Junaid Ahmed, 1 year ago
While trying to lookup 'wlsb.internal.transport.task.queue.file' didn't find subcontext 'wlsb'. Resolved ''; remaining name 'wlsb/internal/transport/task/queue/file'
via Oracle Community by 930163, 1 year ago
While trying to lookup 'wlsb.internal.transport.task.queue.file' didn't find subcontext 'wlsb'. Resolved ''; remaining name 'wlsb/internal/transport/task/queue/file'
via Oracle Community by 946124, 1 year ago
While trying to lookup 'wlsb.internal.transp ort.task.queue.file' didn't find subcontext 'wlsb'. Resolved ''; remaining name 'wlsb/internal/transport/task/queue/file'
via Oracle Community by Vinod Kumar Kashyap, 11 months ago
While trying to lookup 'stellent.command/configuration' didn't find subcontext 'stellent'. Resolved ''; remaining name 'stellent/command/configuration'
javax.naming.NameNotFoundException: While trying to lookup 'wlsb.internal.transport.task.queue.file' didn't find subcontext 'wlsb'. Resolved ''; remaining name 'wlsb/internal/transport/task/queue/file' 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)