IV22989: WEBSPHERE MQ V7.1 CLASSES FOR JAVA APPLICATION REPORTS MQJE001 COMPLETION CODE 2 REASON 2018 WHEN SENDING MESSAGES

Fix Pack 7.1.0.2 for WebSphere MQ V7.1
WebSphere MQ V7.5 Fix Pack 7.5.0.1

APAR status

• Closed as program error.

Error description

• A WebSphere MQ V7.1 classes for Java application is running,
  and the following message is logged:
  
  MQJE001: Completion Code '2', Reason  '2018'
  
  when sending messages to a WebSphere MQ queue.  The messages do
  make it to the destination queue.  There are no FDCs or queue
  manager errors reported.
  
  Trace details report the following exception as having been
  thrown:
  
  Throwing Exception: com.ibm.mq.MQException: MQJE001: Completion
  Code '2', Reason '2018'.
  com.ibm.mq.MQManagedObject.close(MQManagedObject.java:408)
  com.ibm.mq.MQManagedObject.finalize(MQManagedObject.java:442)
  com.ibm.mq.MQQueueManager.finalize(MQQueueManager.java:4416)
  java.lang.J9VMInternals.runFinalize(J9VMInternals.java:408)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users connecting to WebSphere MQ V7 queue manager from WebSphere
  MQ Classes for Java, where the application connects and
  disconnects from the queue manager more than once.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
  ****************************************************************
  PROBLEM SUMMARY:
  The WebSphere MQ classes for Java keeps an internal list of
  connections which have been made to the queue manager.  When
  the connections were no longer needed, the entries in this list
  may have been cleared without fully closing the associated
  connection to the queue manager.
  
  At a later time, the JVM garbage collection thread later found
  these unreferenced connection objects, and runs the associated
  finalize method, the 'hconn' may have been disconnected, which
  results in a MQRC 2018 message being output (MQRC_HCONN_ERROR).
  

Problem conclusion

• The code fix associated with this APAR ensures that the internal
  queue managers connection list is not cleared until it has been
  completely closed.
  
  The result of this is that there are no unusable queue manager
  connection objects left in the memory, and so the problem does
  not occur when the JVM garbage collector thread runs.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.1
  Platform           Fix Pack 7.1.0.2
  --------           --------------------
  Windows            U200351
  AIX                U853019
  HP-UX (Itanium)    U853052
  Solaris (SPARC)    U853048
  Solaris (x86-64)   U853054
  iSeries            7.1.0.2
  Linux (x86)        U853049
  Linux (x86-64)     U853053
  Linux (zSeries)    U853050
  Linux (Power)      U853051
  zOS                7.1.0.2
  
  Platform           v7.5
  --------           --------------------
  Multiplatforms     7.5.0.1
  
  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 AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R710 PSY

     UP