IBM Support

IC64838: NULLPOINTEREXCEPTION CAUSES WEBSPHERE MQ APPLICATIONS TO HANG OR PERFORM SLOWLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following NullPointerException is reported and it causes
    WebSphere MQ applications to appear hung, or to process very
    slow.  In this case the MQ Application was WebSphere MQ File
    Transfer Edition.
    
    The exception observed is:
    java.lang.NullPointerException
    [10/11/2009 21:23:51:269 ACT] 0000000c StdErr        E    at
    com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.
    asyncFailureNotify(RemoteConnection.java:3141)
    
    [10/11/2009 21:23:51:269 ACT] 0000000c StdErr        E    at
    com.ibm.mq.jmqi.remote.internal.RemoteRcvThread.
    run(RemoteRcvThread.java:527)
    
    [10/11/2009 21:23:51:284 ACT] 0000000c StdErr        E    at
    java.lang.Thread.run(Thread.java:810)
    

Local fix

  • Kill the process and restart it.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    User of WebSphere MQ v7.0 Java client applications who are
    making synchronous calls to a queue manager requesting messages.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    For a WebSphere MQ Java client operating in a strictly
    synchronous mode, when a client to server disconnection is
    detected, an attempt is made to notify any asynchronous threads
    of the disconnection event.
    
    For cases where no asynchronous threads existed, the
    notification mechanism had not been instantiated and a
    NullPointerException was thrown from
    RemoteConnection.asyncFailureNotify(), with the following stack
    trace (from WebSphere MQ v7.0.1.0 client level of code):
    
    Exception in thread "RcvThread:
    com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection[qmid=QM_MQ
    
    ,fap=10,peer=peername,localport=1053,ssl=no]"
    java.lang.NullPointerException
    at
    com.ibm.mq.jmqi.remote.internal.system.RemoteConnection
    .asyncFailureNotify(RemoteConnection.java:3141)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteRcvThread
    .run(RemoteRcvThread.java:527)
    at java.lang.Thread.run(Thread.java:810
    

Problem conclusion

  • A code change was made which prevents the notification system
    from being invoked from this code point if it has not been
    instantiated.
    
    Note that a similar event in another code area could also occur
    under these same circumstances.  This was addressed in APAR
    IC64613.
    
    
    ---------------------------------------------------------------
    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 number

    IC64838

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-26

  • Closed date

    2009-11-30

  • Last modified date

    2009-12-16

  • 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

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 December 2009