java.io.IOException

Recipient not connected 4098


Solutions on the web6162

Solution icon of github
Recipient not connected 4098

Solution icon of github
via GitHub by ruanpienaar
, 1 year ago
Not connected

Solution icon of sourceforge
Not connected.

Solution icon of sourceforge
Not connected.

Solution icon of github
Not connected.

Solution icon of sourceforge
via openvpn-als by arrmo
, 1 year ago
Not connected.

Solution icon of coderanch
via Coderanch by kapil munjal, 8 months ago
Client is not connected

Solution icon of googlegroups
via Google Groups by Unknown author, 4 weeks ago
Session not connected

Solution icon of googlegroups
via Google Groups by je...@mertz.fm (JIRA), 9 months ago
Pipe not connected

Solution icon of googlegroups
Client is not connected

Stack trace

  • java.io.IOException: Recipient not connected 4098 at org.objectweb.proactive.core.remoteobject.RemoteObjectAdapter.receiveMessage(RemoteObjectAdapter.java:187) at org.objectweb.proactive.core.remoteobject.SynchronousProxy.reify(SynchronousProxy.java:82) at pa.stub.org.objectweb.proactive.extensions.dataspaces.core.naming._StubNamingService.unregister(_StubNamingService.java) at org.objectweb.proactive.extensions.dataspaces.core.naming.CachingSpacesDirectory.unregister(CachingSpacesDirectory.java:136) at org.objectweb.proactive.extensions.dataspaces.core.NodeConfigurator$NodeApplicationConfigurator.close(NodeConfigurator.java:372) at org.objectweb.proactive.extensions.dataspaces.core.NodeConfigurator$NodeApplicationConfigurator.access$300(NodeConfigurator.java:310) at org.objectweb.proactive.extensions.dataspaces.core.NodeConfigurator.tryCloseAppConfigurator(NodeConfigurator.java:256) at org.objectweb.proactive.extensions.dataspaces.core.NodeConfigurator.configureApplication(NodeConfigurator.java:190) at org.objectweb.proactive.extensions.dataspaces.core.DataSpacesNodes.configureApplication(DataSpacesNodes.java:170) at org.ow2.proactive.scheduler.task.launcher.TaskLauncher.initDataSpaces(TaskLauncher.java:728) at org.ow2.proactive.scheduler.task.launcher.NativeTaskLauncher.doTask(NativeTaskLauncher.java:121) at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.objectweb.proactive.core.mop.MethodCall.execute(MethodCall.java:399) at org.objectweb.proactive.core.body.request.RequestImpl.serveInternal(RequestImpl.java:257) at org.objectweb.proactive.core.body.request.RequestImpl.serve(RequestImpl.java:201) at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serveInternal(BodyImpl.java:626) at org.objectweb.proactive.core.body.BodyImpl$ActiveLocalBodyStrategy.serve(BodyImpl.java:587) at org.objectweb.proactive.core.body.AbstractBody.serve(AbstractBody.java:949) at org.objectweb.proactive.Service.blockingServeOldest(Service.java:180) at org.objectweb.proactive.Service.blockingServeOldest(Service.java:155) at org.objectweb.proactive.Service.fifoServing(Service.java:131) at org.objectweb.proactive.core.body.ActiveBody$FIFORunActive.runActivity(ActiveBody.java:323) at org.objectweb.proactive.core.body.ActiveBody.run(ActiveBody.java:203) at java.lang.Thread.run(Thread.java:619)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.