JR53918: THREADS HANG IN GROUPCORE.PROCESSDELETEUSERGROUPS WHILE THE SERVER STARTS
Direct links to fixes
Closed as program error.
You might experience threads hanging while the server starts as the server tries to synchronize a large number of user group definitions (more than 50 thousand entries) and the number of retrieved groups is greater than the number of groups already available in the database. You might see hanging threads with the following stack trace: Thread "server.startup : 0" (00000011) has been active for 702995 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.util.LinkedList.contains(LinkedList.java:485) at java.util.AbstractSet.removeAll(AbstractSet.java:106) at com.lombardisoftware.server.core.GroupCore. processDeletedUserGroups(GroupCore.java:631) at com.lombardisoftware.server.core.GroupCore. getAllGroupsInternal(GroupCore.java:593) at com.lombardisoftware.server.core.GroupCore. getAllGroups(GroupCore.java:572)
While the server starts, IBM BPM synchronizes all group definitions between the applied user registry and the IBM BPM database. Before these updates take effect in the database, IBM BPM updates the set of groups already available in the database by removing entries from the set of groups retrieved from the applied user registry. Because a Java core function is used that performs very slowly, Java threads might hang if the number of retrieved groups is greater than the number of groups already available in the database and both the number of already available groups and the retrieved groups is very large, such as more than 50 thousand entries.
A fix is available for IBM BPM V220.127.116.11 that ensures even large existing group definitions are processed efficiently by using a different group-removal procedure. This procedure ensures the processing time is linear depending on the number of group entities. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR53918: 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 JR53918, 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.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels