Fixes are available
APAR status
Closed as program error.
Error description
Reassigning a task back to the same set of users as defined (as potential owners of the task) before the task was claimed fails, leaving the task not operable, i.e. unclaimable. . This may also result in the following exception when trying to display the tasks. . [1/22/13 10:40:01:529 FNT] 0000008d servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /jsp/tiles/ProcessDetails.jsp in application IBM_BPM_Portal_bps.AppTarget. Exception created : java.lang.NullPointerException at com.ibm._jsp._ProcessDetails._jspService(_ProcessDetails. java:1048) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service (ServletWrapper.java:1657) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service (ServletWrapper.java:1597) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter (WebAppFilterChain.java:104) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter (WebAppFilterChain.java:77) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter (WebAppFilterManager.java:908) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (ServletWrapper.java:934) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (ServletWrapper.java:502)
Local fix
N/A
Problem summary
Problem Description: When defining task assignment (aka task routing) in terms of a custom user list, the sequence of claiming the task and assigning it back to the initial custom user list will result in the task not being assigned to any user or role, thus rendering the task not operable. Problem Summary: Custom user lists are internally mapped onto ad-hoc groups. In order to keep the number of ad-hoc group low, such groups are deleted internally after claiming a task. Such deletion concerns DB entries, but not the group entries maintained in a memory cache. When reassigning the task back to the initial custom user list, the initial ad-hoc group is found in the memory cache, but has no entry in the database. Problem Conclusion: The deletion of the ad-hoc group is removed, so that cach and database entries fr the ad-hoc group never get out of sync. Removal of unnecessary ad-hoc groups is covered by a separate mechanism.
Problem conclusion
Problem fixed iFix available on top of V751 FP1
Temporary fix
Comments
APAR Information
APAR number
JR45349
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-11
Closed date
2013-01-31
Last modified date
2013-02-05
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 ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R751 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021