A fix is available
APAR status
Closed as program error.
Error description
A sender channel is defined with multiple CONNAMEs(e.g. two remote hosts and ports) with LOCLADDR((12345,12445)). A connection attempt to the first host fails because of an error(e.g. AMQ9558 or host is not available etc) and then the channel tries to connect to the 2nd host. But the sender channel fails with the following error: AMQ9248: The program could not bind to a TCP/IP socket. EXPLANATION: The attempt to bind to socket '1.2.3.4(12345)' failed with return code 98. The failing TCP/IP call was 'bind'. The most likely cause of this problem is incorrect configuration of the TCP/IP local address or incorrect start and end port parameters. A trace of the queue manager reveals that the only port number that is used is the lower limit, in this case 12345. Notice that an incorrect range is being actually used, which is really a range of only 1 port: No free port numbers in range 12345 to 12345 ... instead of the desired 100 ports (the upper bound should be 12445 and not 12345): . 14:47:29.210998 14958.1 RSESS:000000 Attempting to bind to address 'x' port 12345 14:47:29.211001 14958.1 RSESS:000000 -----{ bind 14:47:29.211008 14958.1 RSESS:000000 -----}! bind rc=Unknown(FFFFFFFF) 14:47:29.211014 14958.1 RSESS:000000 No free port numbers in range 12345 to 12345
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users using multiple CONNAMEs with LOCLADDR defined with multiple port numbers Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: This problem occurred because the connection was retried with the last port used from the previous connection attempt instead of the starting port of the defined local port range. The connection should be retried with the local ports configured.
Problem conclusion
MQ channel code has been modified to initialize the LOCLADDR correctly when the connection is retried. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.5 7.5.0.5 v8.0 8.0.0.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
IT05668
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7241
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-19
Closed date
2014-12-31
Last modified date
2015-11-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
WMQ BASE MULTIP
Fixed component ID
5724H7241
Applicable component levels
R750 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]
Document Information
Modified date:
25 September 2021