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 3004, 1 year ago
The object identified by [9] could not because found. Either it was has not been exported or it has been collected by the distributed garbage collector.
via Google Groups by Chris Goodacre, 9 months ago
The object identified by: '9' could not because found. Either it was has not been exported or it has been collected by the distributed garbage collector.
via Oracle Community by 3004, 9 months ago
The object identified by: '9' could not because found. Either it was has not been exported or it has been collected by the distributed garbage collector.
via Oracle Community by 3004, 9 months ago
The object identified by [9] could not because found. Either it was has not been exported or it has been collected by the distributed garbage collector.
via wosoni.com by Unknown author, 1 year ago
The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.
via Oracle Community by Laus, 1 year ago
The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
java.rmi.NoSuchObjectException: The
object identified by [9] could not because found. Either it was has not been exported or it has been
collected by the distributed garbage collector.	at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:401)	at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLInitialContextFactoryDelegate.java:315)	at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:275)