APAR status
Closed as program error.
Error description
RDQM creation fails with following errors crtmqm -sx -fs 128M RDQM2 Creating replicated data queue manager configuration. AMQ3879E: Resource 'rdqm2' not connected to 'DRHA21.fyre.ibm.com' after '10' seconds. AMQ3812E: Failed to create replicated data queue manager configuration. and system log records the following error Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: Starting receiver thread (from drbd_w_rdqm3 [7396]) Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: conn( Unconnected -> Connecting ) Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: Failed to initiate connection, err=-98 Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: conn( Connecting -> Disconnecting ) Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: Aborting remote state change 0 commit not possible Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: Restarting sender thread Jun 24 01:16:10 DRHA11 kernel: drbd rdqm2 xxx.com: Failed to initiate connection, err=-98
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All IBM MQ users who use Replication Data Queue Manager (RDQM) feature. Platforms affected: Linux on x86-64 **************************************************************** PROBLEM DESCRIPTION: When RDQM is created it picks a port in the range of 7000 for using it for its DRBD connection, however, if this port is in use by another application then the queue manager creation fails while it tries to establish the DRBD connection with the Secondary nodes.
Problem conclusion
The code is modified to verify if the port is in use by another process before it is picked for drbd connection. If the port is already in use then an exclude list is created to omit ports that are in use. The crtmqm command will fail with AMQ6543 error message. The user should reissue the crtmqm command after deleting the RDQM from the secondary nodes. Following is the description of the error AMQ6543 536896835 0x20006543 aplE_PORT_IN_USE MESSAGE: Port '1111' is in use. EXPLANATION: The command failed because port number '1111' is currently in use. ACTION: Reissue the command with a port number that is not in use. For crtmqm -sx(s), the first crtmqm -sxs automatically selects the replication port to use. It chooses the next free port from 7000. This error indicates that the port that was chosen is one that is in use on this node. The port is added to an exclude list. The secondary queue manager(s) should be deleted and recreated on the other node(s). --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.1 LTS 9.1.0.7 v9.x CD 9.2.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT33347
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7271
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-06-28
Closed date
2020-10-21
Last modified date
2020-10-21
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
IBM MQ BASE MP
Fixed component ID
5724H7271
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
23 October 2020