APAR status
Closed as program error.
Error description
Description: The AdminAgent (bipbroker) process may abend after making configuration changes to an integration server that uses monitoring profiles with applications and message flows. These changes may include activating and deactivating message flow monitoring or stopping and starting applications. When these changes are made, the AdminAgent process has to refresh its repository cache to reflect the changes. This may lead to intermittent abends with a call stack similar to the following: ImbDeployManagerCacheEventRecord::equals ImbDeployManagerCache::notifyEventListenersOfUpdates ImbDeployManagerCache::refreshExecutionGroup ImbDeployManagerCacheRefreshThread::refreshExecutionGroup ImbDeployManagerCacheRefreshThread::run ImbThreadPoolThreadFunction::run ImbOsThread::threadRun
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus using event monitoring. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The AdminAgent (bipbroker) process may abend after making configuration changes to an integration server that uses monitoring profiles with applications and message flows. These changes may include activating and deactivating message flow monitoring or stopping and starting applications. When these changes are made, the AdminAgent process has to refresh its repository cache to reflect the changes. This may lead to intermittent abends with a call stack similar to the following: ImbDeployManagerCacheEventRecord::equals ImbDeployManagerCache::notifyEventListenersOfUpdates ImbDeployManagerCache::refreshExecutionGroup ImbDeployManagerCacheRefreshThread::refreshExecutionGroup ImbDeployManagerCacheRefreshThread::run ImbThreadPoolThreadFunction::run ImbOsThread::threadRun Each monitoring event has a map of referenced message flows and there should be only one entry per message flow. But duplicate references to the same message flow are being inserted. Then when a message flow reference is removed from the event, during a deploy, only one of the entries in the map is being removed leaving some message flow entries pointing at a message flow cache object that no longer exists.
Problem conclusion
The product now prevents duplicate references to the same message flow from being inserted into the event map. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.15 v11.0 11.0.0.3 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT23242
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-21
Closed date
2018-12-18
Last modified date
2018-12-18
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
18 December 2018