IC68871: MQJMS2005 AND MQJE001 RC=2059 WHEN USING WMQ V7.0.1.0 OR V7.0.1.1 TO CONNECT WITH A CF USING A CONNECTION NAME LIST

WebSphere MQ V7.0 Fix Pack 7.0.1.4
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.4

APAR status

• Closed as program error.

Error description

• When using WebSphere MQ (WMQ) v7.0.1.0 or v7.0.1.1 to create a
  connection factory (CF) which uses a connection name list, an
  attempt to connect to a queue manager using that connection
  factory with a client that is prior to MQ v7.0.1.0 will fail.
  
  The hostname in the connection list is not used. The error
  message identifies "localhost" instead of the hostname.  The
  error will look similar to this:
  
  Initial context found!
  javax.jms.JMSException: MQJMS2005: failed to create
  MQQueueManager for 'localhost:'.
  Inner exception(s):
  com.ibm.mq.MQException: MQJE001: Completion Code '2',
  Reason '2059'.
  com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;
  AMQ9204: Connection to host  'localhost(1414)' rejected.
  [1=com.ibm.mq.jmqi.JmqiException [CC=2;RC=2059;
  AMQ9213: A communications error for  occurred
  [1=java.net.ConnectException[Connection refused:
  connect],3=localhost]],3=localhost(1414),
  5=RemoteTCPConnection.connnectUsingLocalAddress]
  
  com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;
  
  java.net.ConnectException: Connection refused: connect
  FAILURE
  
  ADDITIONAL KEYWORDS: WMQCF AMQ9204 AMQ9213 local host
  MQRC_Q_MGR_NOT_AVAILABLE JmqiException
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WMQ classes for Java Message
  Service (JMS) who create a connection factory JNDI
  definition at WMQ v7.0.1.0 or v7.0.1.1.  The 'client'
  transport type is used and the CONNECTIONNAMELIST specifies
  connection details other than localhost(1414).  The connection
  factory definition is subsequently used by a WMQ Client earlier
  than 7.0.1.0.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  From WMQ v7.0.1.0, the CONNECTIONNAMELIST property on the
  connection factory was introduced as part of the Automatic
  client reconnection functionality.  This property replaced the
  HOSTNAME and PORT properties which were previously used to
  specify connection details, although the HOSTNAME and PORT
  properties still exist for backward compatibility.
  
  When creating a connection factory and specifying a
  CONNECTIONNAMELIST, the HOSTNAME and PORT properties were left
  at their default values of "localhost" "1414".  When a client
  which doesn't recognise the CONNECTIONNAMELIST property (i.e.
  pre v7.0.1.0) used the connection factory, it read the
  HOSTNAME/PORT fields and so tried to connect to localhost(1414).
  

Problem conclusion

• When setting the CONNECTIONNAMELIST, the first entry in the list
  is copied to the HOSTNAME and PORT fields.  This enables older
  clients to use the same connection details that have been set in
  the CONNECTIONNAMELIST.
  
  If the HOSTNAME/PORT fields are modified by a pre v7.0.1.0
  client, a client containing this fix will copy the HOSTNAME/PORT
  values into the first CONNECTIONNAMELIST entry when it loads the
  connection factory.
  
  By doing this, the first entry in CONNECTIONNAMELIST and the
  values in HOSTNAME/PORT will always be in sync.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.2
  --------           --------------------
  Windows            U200316
  AIX                U829807
  HP-UX (PA-RISC)    U829678
  HP-UX (Itanium)    U829681
  Solaris (SPARC)    U829806
  Solaris (x86-64)   U829680
  iSeries            tbc_p700_0_1_2
  Linux (x86)        U829677
  Linux (x86-64)     U829676
  Linux (zSeries)    U829682
  Linux (Power)      U829679
  
  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 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 WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP