"java.rmi.ConnectException: This RJVM has already been shutdown" is randomly thrown when executing PAPI calls from a PAPI application deployed in a separate domain (Doc ID 1309518.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Sep-2012***
***Checked for relevance on 07-February-2014***

Symptoms

When executing PAPI calls from a PAPI application that is deployed in a separate WLS domain (i.e. domain A) than where the Engine is running (in another WLS domain - domain B), the following error message could be thrown when trying to retrieve an instance/normal variable value.

...
Caused by: object_name.exceptions.ServiceException: Error obteniendo una variable interna de una instancia.
at object_name.services.BPMServiceImpl.getVariable(BPMServiceImpl.java:1292)
at object_name.services.BPMServiceImpl.getVariable(BPMServiceImpl.java:1239)
at object_name.services.BPMServiceImpl.getVariable(BPMServiceImpl.java:1216)
at object_name.services.BPMServiceImpl.esTareaCancelable(BPMServiceImpl.java:1429)
at object_name.services.BPMServiceImpl.esTareaCancelable(BPMServiceImpl.java:1404)
... 100 more
Caused by: fuego.papi.OperationRuntimeException: Runtime operation error.
at fuego.papi.impl.InstanceInfoImpl.getNormalVariable(InstanceInfoImpl.java:465)
at fuego.papi.impl.InstanceInfoImpl.getVariable(InstanceInfoImpl.java:291)
at object_name.services.BPMServiceImpl.getVariable(BPMServiceImpl.java:1269)
... 104 more
Caused by: fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
at fuego.papi.impl.j2ee.EJBSecureEngineHandler.doInvoke(EJBSecureEngineHandler.java:146)
at fuego.papi.impl.j2ee.EJBSecureEngineHandler.invoke(EJBSecureEngineHandler.java:56)
at $Proxy146.exportProcessControl(Unknown Source)
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createProcessControl(J2EEEngineAccessImpl.java:152)
at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1118)
at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2709)
at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1714)
at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2714)
at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstance(ProcessServiceSessionImpl.java:2271)
at fuego.papi.impl.util.VariableRetrievalUtils$1.execute(VariableRetrievalUtils.java:60)
at fuego.papi.impl.util.AnySessionOperationUtils.executeOnAnySession(AnySessionOperationUtils.java:35)
at fuego.papi.impl.util.VariableRetrievalUtils.retrieveNormalVariable(VariableRetrievalUtils.java:52)
at fuego.papi.impl.ProcessServiceImpl.instanceGetNormalVar(ProcessServiceImpl.java:1509)
at fuego.papi.impl.InstanceInfoImpl.getNormalVariable(InstanceInfoImpl.java:462)
... 106 more
Caused by: java.rmi.ConnectException: This RJVM has already been shutdown -2098102170965977093S:node_name:[3301,3301,-1,-1,-1,-1,-1]:BPM10:Engine_Name
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:365)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:609)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:560)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:783)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:211)
at fuego.ejbengine.engine_Engine_Name_3zry2r_EOImpl_1030_WLStub.exportProcessControl(Unknown Source)
at fuego.papi.impl.j2ee.EJBSecureEngineInterfaceWrapper.exportProcessControl(EJBSecureEngineInterfaceWrapper.java:369)
at sun.reflect.GeneratedMethodAccessor905.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at fuego.papi.impl.AbstractSecureEngineHandler.invokeInternal(AbstractSecureEngineHandler.java:49)
at fuego.papi.impl.j2ee.EJBSecureEngineHandler.doInvoke(EJBSecureEngineHandler.java:105)

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms