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 704121, 2 years ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
via Oracle Community by kroberts5683, 1 year ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
via myexception.cn by Unknown author, 1 year ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
via Oracle Community by RSOA, 1 year ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
via hivmr.com by Unknown author, 1 year ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
via Oracle Community by 684279, 2 years ago
Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
javax.naming.NameNotFoundException: Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'	at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180)	at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)	at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)	at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)	at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:253)