RMI Connectivity not working after restart

Solution Verified - Updated -

Issue

Some RMI Services are throwing the following exception after server restart:

javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:839)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at TestTaxService.main(TestTaxService.java:26)
Caused by: java.rmi.NoSuchObjectException: no such object in table
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
        at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:734)

This client application is hosted in a different physical machine than the JNDI Server

Environment

  • JBoss SOA-P 4.3.0_CP04

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content