My Oracle Support Banner

While Configuring RMI Cache Coordination for Weblogic in Standalone TopLink Workbench error: "java.lang.NoClassDefFoundError: weblogic/rmi/spi/HostID" (Doc ID 1061687.1)

Last updated on OCTOBER 17, 2011

Applies to:

Oracle TopLink - Version: and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.


You are trying to configure sessions.xml in standalone TopLink Workbench. When checking the Cache Coordination tab to provide the JNDI parameters, the following exception is encountered:

Exception in thread "Thread-0" java.lang.NoClassDefFoundError: weblogic/rmi/spi/HostID
at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.(
at weblogic.jndi.spi.EnvironmentManager.getInstance(
at weblogic.jndi.Environment.getContext(
at weblogic.jndi.Environment.getContext(
at weblogic.jndi.WLInitialContextFactory.getInitialContext(
at javax.naming.spi.NamingManager.getInitialContext(
at javax.naming.InitialContext.getDefaultInitCtx(
at javax.naming.InitialContext.init(
at javax.naming.InitialContext.(
at oracle.toplink.remotecommand.TransportManager.getContext(
at oracle.toplink.remotecommand.rmi.RMITransportManager.getLocalHostContext(
at oracle.toplink.remotecommand.rmi.RMITransportManager.createLocalConnectionInJNDI(
at oracle.toplink.remotecommand.rmi.RMITransportManager.createLocalConnection(

1. This problem would not occur if the application was running inside (deployed to) WebLogic Server.
2. This problem does only occur if the application is running outside of WebLogic Server with no other naming context factory being configured for JNDI.
3. This problem does not occur if some other naming context factory had been configured.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.