Direct links to fixes
APAR status
Closed as program error.
Error description
In a business process definition (BPD) or a process, you can define activities to run even though they don't have an inbound flow. Those activities are also called "ad hoc activities". If you define an ad hoc activity to be manual, it must be started by a user or by using an API. If you start the ad hoc activity by using the JavaScript API within a service that is the implementation of an undercover agent (UCA) and the ad hoc activity is implemented by a subprocess or linked process that has a system task, the API call fails. In the SystemOut.log file of the server, you see an exception like this: [8/3/16 14:03:31:084 SAST] 000002e3 E UOW=null source=WLE.wle org=null prod=null component=null thread=[WorkManager.bpm-em-workmanager : 4] CWLLG2229E: An exception occurred in an EJB call. Error: Task with ID Task.3328 not found. com.lombardisoftware.core.TeamWorksException: Task with ID Task.3328 not found. at com.lombardisoftware.server.ejb.persistence.CommonDAO.assertNotN ull(CommonDAO.java:65) ... at com.lombardisoftware.client.persistence.TaskFactory.findByPrimar yKey(TaskFactory.java:137) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean$ 13.doInTransaction(EJBWorkflowManagerBean.java:2686) ... at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. getTask(EJBWorkflowManagerBean.java:2690) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. doResumeWorkflowEngine(EJBWorkflowManagerBean.java:765) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. doResumeWorkflowEngine(EJBWorkflowManagerBean.java:678) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. resumeTask(EJBWorkflowManagerBean.java:362) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. resumeTask(EJBWorkflowManagerBean.java:326) ... at com.lombardisoftware.bpd.runtime.engine.quartz.ExecuteSystemLane ActivityTask$1.run(ExecuteSystemLaneActivityTask.java:86) ... at com.lombardisoftware.bpd.runtime.engine.quartz.ExecuteSystemLane ActivityTask.execute(ExecuteSystemLaneActivityTask.java:100) at com.lombardisoftware.server.scheduler.Engine.execute(Engine.java :1013) ... If you define an ad hoc activity to be required, it must be completed for the process to complete. In an exceptional situation, an administrator might decide to overrule this process completion by disabling an activity. A disabled activity can be enabled again. If the ad hoc activity has a pre-condition based on a variable expression, an exception occurs if this condition is true while the ad hoc activity is disabled.
Local fix
Problem summary
No additional information is available. PRODUCTS AFFECTED IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Problem conclusion
A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.09 that ensures the start ad hoc activity API works correctly from a UCA service implementation and that pre-conditions are correctly evaluated when an activity is enabled. To determine whether the cumulative fix is available and download it if it is, complete the following steps on Fix Central: 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 Text, enter ?cumulative fix?, and click Continue.
Temporary fix
Comments
APAR Information
APAR number
JR56510
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-17
Closed date
2016-09-20
Last modified date
2016-09-20
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 September 2023