Direct links to fixes
APAR status
Closed as program error.
Error description
When you start an IBM Business Process Manager (BPM) application cluster or stand-alone server, the IBM BPM related applications start, which involves certain initialization steps. In rare cases, these operations might lock each other and cause group synchronization to fail. In the SystemOut.log file of the server, you find stack traces similar to the following stack traces: [09/02/16 06:26:05:208 CET] 000000f1 GroupCore E com.lombardisoftware.server.core.GroupCore ExternalGroupSynchronizer:run synchronization of external group fails with: com.lombardisoftware.core.TeamWorksException: Problems during replication of Groups, resetting Group Info cache at com.lombardisoftware.server.core.GroupCore. getAllGroupsInternal(GroupCore.java:1498) Caused by: com.lombardisoftware.client.delegate.BusinessDelegateException: Some object reference in the name "ejb/PersistenceServices" relative to the context "cell/clusters/PRD001.AppTarget" is invalid. Some possible causes include a context binding in the name which refers to a destroyed context, or an object binding which contains an invalid EJBHome reference.
Local fix
After your application server has started, you can stop and restart the IBM BPM Teamworks application from the administrative console. Note: The application name depends on your node and server name and follows the naming schema IBM_BPM_Teamworks_<appTarget> where <appTarget> either is the application cluster name (IBM BPM Advanced or IBM BPM Standard) or the node name and server name of the stand-alone server (IBM BPM Express or IBM Integration Designer).
Problem summary
The group synchronization launched while the server started requires access to a EJB resource. If the EJB is not available, the thread must wait and a lock on the EJB cache is set. If the group synchronization is started too early, this lock prevents the server startup thread from updating the EJB cache and completing the load of the EJB. After two minutes, the group synchronization thread stops with a timeout and the lock is released. The server thread finishes the start up procedure, but the group synchronization fails.
Problem conclusion
A fix is available for IBM BPM V8.5.6.0 Cumulative Fix 2 that changes the initialization sequence to run the group synchronization only when all resources are available. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR55293: 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 JR55293 , 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
JR55293
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
856
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-17
Closed date
2016-04-07
Last modified date
2016-04-07
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
R856 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 April 2016