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 Google Groups by muhammad aqib, 2 years ago
Unable to resolve 'WebLogicSes' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'
via Oracle Community by 843830, 2 years ago
Unable to resolve 'WebLogicSes' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'
via Oracle Community by 666705, 1 year ago
Unable to resolve 'WebLogicSes' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'
via Oracle Community by 666705, 2 years ago
Unable to resolve 'WebLogicSes' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'
via Oracle Community by 666705, 2 years ago
Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'
javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'WebLogicSes' Resolved ]; remaining name 'WebLogicSes'	at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)	at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)