APAR status
Closed as program error.
Error description
The problem is caused when WebSphere Message Broker times out trying to obtain a lock on its file system so it can commit the deployment to its configuration store. This is followed by an automatic retry of that deploy, but the retry fails because WebSphere Message Broker is not expecting to find a reference to the new flow in its cached memory.
Local fix
IBM suggested a work-around to increase the time-out interval for obtaining a write lock on the WebSphere Message Broker configuration store. The default time-out interval is 6 seconds. The problem did not reoccur after increasing the time-out interval. This is an example of using an environment variable to increase the time-out to 12 seconds. The value is configured in milliseconds: MQSI_CONFIGSTORE_THREAD_TIMEOUT=12000 IBM Supplied a fix that removes the failed deploy of a new message flow from memory when a time-out occurs obtaining a lock on the configuration store.
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Message Broker V7.0 and above, performing batch deploys of multiple message flows to a single execution group. Platforms affected: MultiPlatform **************************************************************** PROBLEM SUMMARY: When deploying a large batch of message flows one of the deployments times out. This causes a failure with the following sequence of error messages: BIP2112E <broker> <execution group> MESSAGE BROKER INTERNAL ERROR: DIAGNOSTIC INFORMATION 'CS0010', 'Failed to obtain a write lock due to a timeout.' BIP2153I <broker> <execution group> ABOUT TO 'change' AN EXECUTION GROUP. BIP2155I <broker> <execution group> ABOUT TO 'create ' THE MESSAGE FLOW - '<flow name>'. BIP4041E <broker> <execution group> EXECUTION GROUP '<execution group>' RECEIVED AN INVALID CONFIGURATION MESSAGE. SEE THE FOLLOWING MESSAGES FOR DETAILS OF THE ERROR. BIP2262E <broker> <execution group> REQUEST TO CREATE MESSAGE FLOW '<flow name>' (UUID='<execution group UUID>'): MESSAGE FLOW ALREADY EXISTS. When the timeout occurs the state of the failed deployment is not correctly backed out of memory. So when the deployment is retried the Broker generates a BIP2262E message to report that the message flow already exists.
Problem conclusion
WebSphere Message Broker has been modified so that a failed deployment is correctly backed out when a time-out occurs. This enables a subsequent retry to complete successfully. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Platform v7.0 -------- -------------------- Multiplatforms 7.0.0.6 Platform v8.0 -------- -------------------- Multiplatforms 8.0.0.3 The latest available maintenance can be obtained from 'WebSphere Message Broker Recommended Fixes' http://www.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 in 'WebSphere Message Broker Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
PM79743
Reported component name
WEB MB Z/OS
Reported component ID
5655V6000
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-26
Closed date
2013-01-31
Last modified date
2013-01-31
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
WEB MB Z/OS
Fixed component ID
5655V6000
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7.0"}]
Document Information
Modified date:
29 October 2021