Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…


It is impossible to connect to the Runtime from a Designer, but the Runtime process seems to be running.

The Runtime logs contain an error "java.rmi.NoSuchObjectException: no such object in table".

java.rmi.NoSuchObjectException: no such object in table
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:273)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:251)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160)
    at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:194)
    at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:148)
    at $Proxy1.executeDelivery(Unknown Source)
    at com.indy.engine.scheduler.jobs.RemoteDeliveryExecutionJob.execute(RemoteDeliveryExecutionJob.java:90)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)



This can happen when there was some network failure which caused the Runtime to partially stop. This can also happen after the Runtime's host machine went to sleep.

The best way to recover from this case is to stop and restart the Runtime.

To avoid this in the future, make sure that the Runtime's host machine never goes to sleep.


Knowledge Base

Suggest a new Article!