Direct links to fixes
APAR status
Closed as program error.
Error description
You receive an UnexpectedFailureException when you work with tasks by using REST API. The following stack trace can be seen in the log files: RestHelper     X   Encounteredexception has message: java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST 0x0 No; nested exception is: org.omg.CORBA.OBJECT_NOT_EXIST: java.rmi.NoSuchObjectException: Stateful bean BeanId(IBM_BPM_Teamworks_BPM.AppTarget#twcore-ejb. jar#EJBWorkflowManager, 605023C6-0150-4000-E000-73340A648201) was removed or timed out.  vmcid: 0x0  minor code: 0  completed: No java.lang.RuntimeException: java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST 0x0 No; nested exception is: org.omg.CORBA.OBJECT_NOT_EXIST: java.rmi.NoSuchObjectException: Stateful bean BeanId(IBM_BPM_Teamworks_BPM.AppTarget#twcore-ejb. jar#EJBWorkflowManager, 605023C6-0150-4000-E000-73340A648201) was removed or timed out.  vmcid: 0x0  minor code: 0  completed: No at com.ibm.bpm.rest.impl.service.ServiceRunner$TaskRunner. runService(ServiceRunner.java:713) at com.ibm.bpm.rest.impl.task.StartActionHandler. handleAction(StartActionHandler.java:126) at com.ibm.bpm.rest.impl.task.TaskResource.processTaskAction (TaskResource.java:386) at sun.reflect.GeneratedMethodAccessor585.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.wink.server.internal.handlers.InvokeMethodHandler. handleRequest(InvokeMethodHandler.java:51) at org.apache.wink.server.handlers.AbstractHandler. handleRequest(AbstractHandler.java:33) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain. doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers. CreateInvocationParametersHandler.handleRequest (CreateInvocationParametersHandler.java:48) at org.apache.wink.server.handlers.RequestHandlersChain. handle(Requ estHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain. doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers. FindResourceMethodHandler.handleSubResourceMethod (FindResourceMethodHandler.java:178) at org.apache.wink.server.internal.handlers. FindResourceMethodHandler.handleRequest (FindResourceMethodHandler.java:105) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain. doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers. FindRootResourceHandler.handleRequest (FindRootResourceHandler.java:93) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain. handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain. doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers.HeadMethodHandler. handleRequest(HeadMethodHandler.java:53) at org.apache.wink.server.handlers.RequestHandlersChain.handle (RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle (RequestHandlersChain.java:22) ...
Local fix
Problem summary
The session for the EJB that is running a business process definition (BPD) task's implementation expires because the WebSphere EJB session timed out. However, IBM BPM still refers to the EJB instance in its cache. This situation might happen if, for example, users work with a task, but the interactions between browser and server fail for some reason (perhaps because of a wrong parameter) and the service does not complete properly. In this case, the EJB created for the task remains in the cache for later resumption. If the subsequent call to resume working on the task is then made in the same HTTP session but after the WAS EJB session expired, a java.rmi.NoSuchObjectException occurs.
Problem conclusion
A fix is/will be available for IBM BPM V.7.5.1.2 and IBM BPM V.8.5.5.0 that retrieves a new EJB instance when the cached one expires. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR54688: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR54688, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Not applicable
Comments
APAR Information
APAR number
JR54688
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-09
Closed date
2016-01-13
Last modified date
2016-01-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
R751 PSY
UP
R855 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 October 2021