IC64613: NULLPOINTEREXCEPTION RECEIVED WHEN THE JAVA CLIENT HAS DISCOVERED THAT THE TCP CONNECTION TO THE WMQ SERVER IS BROKEN

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

APAR status

• Closed as program error.

Error description

• A NullPointerException occurs when the Java client has
  discovered that the TCP connection to the WebSphere MQ server
  has been broken while running in an synchronous MQGET mode of
  operation.
  
  The following stack trace is seen:
  
  java.lang.NullPointerException
  at
  com.ibm.mq.jmqi.remote.internal.RemoteHconn.exchangeTSH
  (RemoteHconn.java :1444)
  at
  com.ibm.mq.jmqi.remote.internal.system.RemoteProxyQueue.requestM
  essages(RemoteProxyQueue.java:1047)
  at
  com.ibm.mq.jmqi.remote.internal.system.RemoteProxyQueue.flushQue
  ue(RemoteProxyQueue.java:1880)
  at
  com.ibm.mq.jmqi.remote.internal.system.RemoteProxyQueue.proxyMQG
  ET(RemoteProxyQueue.java:2664)
  at
  com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiGetMessageWithProp
  s(Remote  FAP.java:7198)
  at
  com.ibm.mq.jmqi.remote.internal.RemoteFAP.MQGET(RemoteFAP.java:7
  044)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of WebSphere MQ v7 who are using Java
  clients to connect in CLIENT mode to a WebSphere MQ Queue
  Manager, including users of WebSphere MQ File Transfer Edition.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  Internally the Java client has two modes of operation when
  requesting messages, synchronous or asynchronous mode.
  
  When a disconnection between the client and server is detected,
  any asynchronous users are required to be informed of the event.
  However, when operating in the pure synchronous mode there was
  no mechanism instantiated by which to inform any asynchronous
  users.  Thus when the attempt was made to invoke this mechanism,
  a NullPointerException was thrown by the Java Virtual Machine.
  

Problem conclusion

• A code change was made so that the asynchronous user
  disconnection detection mechanism is not invoked when operating
  in the synchronous mode, so the NullPointerException is no
  longer thrown.
  
  
  ---------------------------------------------------------------
  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