Fixes are available
APAR status
Closed as program error.
Error description
If the Client connection channel is defined with a list of hostname/ip addresses in CONNAME and a JMS client application uses channel client definition table (CCDT) to connect to the Queue Manager then the application tries to connect in alphabetical order instead of using the order they are specified in the connection list. This does not match the InfoCenter: Websphere MQ -> Script(MQSC) Command Reference -> The MQSC commands -> DEFINE CHANNEL -> Parameter description -> CONNAME paragraph. For instance: DEF CHANNEL(CH.CLIENT) CHLTYPE(CLNTCONN) CONNAME('hostB,hostA') The application first tries to connect using 'hostA' ( alphabetical order) instead of using the order they are specified in the connection list i.e. hostB then hostA. This could affect performance of the application if the queue manager on hostA is not available.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of the below environments specifying a connection namelist within a Client Channel Definition Table. - The WebSphere MQ V7.0.1 classes for Java/JMS. - The WebSphere MQ V7.0.1 Resource Adapter. - The WebSphere Application Server V7 and V8 WebSphere MQ messaging provider. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: The algorithm which sorts entries within a Client Channel Definition Table (CCDT) invalidly sorted connections within a connection name list in alphabetical order. When a connection attempt was made, this resulted in connections being attempted in alphabetical order.
Problem conclusion
The sorting algorithm has been altered to ensure that connections are sorted in the order specified within a connection name list when using a CCDT, matching the behavior documented in the InfoCenter. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.11 -------- -------------------- Windows 7.0.1.11 AIX 7.0.1.11 HP-UX (PA-RISC) 7.0.1.11 HP-UX (Itanium) 7.0.1.11 Solaris (SPARC) 7.0.1.11 Solaris (x86-64) 7.0.1.11 iSeries 7.0.1.11 Linux (x86) 7.0.1.11 Linux (x86-64) 7.0.1.11 Linux (zSeries) 7.0.1.11 Linux (Power) 7.0.1.11 zOS 7.0.1.11 v7.1 Platform Fix Pack 7.1.0.3 -------- -------------------- Windows 7.1.0.3 AIX 7.1.0.3 HP-UX (Itanium) 7.1.0.3 Solaris (SPARC) 7.1.0.3 Solaris (x86-64) 7.1.0.3 iSeries 7.1.0.3 Linux (x86) 7.1.0.3 Linux (x86-64) 7.1.0.3 Linux (zSeries) 7.1.0.3 Linux (Power) 7.1.0.3 zOS 7.1.0.3 Platform v7.5 -------- -------------------- Multiplatforms 7.5.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
IV38739
Reported component name
WMQ SOL SPARC
Reported component ID
5724H7223
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-28
Closed date
2013-04-10
Last modified date
2013-05-13
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 SOL SPARC
Fixed component ID
5724H7223
Applicable component levels
R701 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.0.1"}]
Document Information
Modified date:
03 October 2021