IBM Support

IC68653: JMSWMQ1107 COM.IBM.MSG.CLIENT.JMS.DETAILEDILLEGALSTATEEXCEPTION JAVA.LANG.NULLPOINTEREXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following error and FFST is seen:
    
    com.ibm.msg.client.wmq.internal.WMQXAConnection
    Exception ignored as no exception listener is registered:
    
    Message : com.ibm.msg.client.jms.DetailedIllegalStateException:
    JMSWMQ1107:
    A problem with this connection has occurred. An error has
    occurred with the WebSphere MQ JMS connection. Use the linked
    exception to determine the cause of this error.
    ----------------------------------------------------------------
    java.lang.NullPointerException at
    com.ibm.mq.jmqi.remote.internal.system.RfpTSH.
    setControlFlags1(RfpTSH.java:497)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.spiNotify
    (RemoteFAP.java:3916)
    ****************************************************************
    Faliure 1:
    ----------------------------------------------------------------
    java.lang.NullPointerException
    at
    com.ibm.mq.jmqi.remote.internal.system.RfpTSH.
    setControlFlags1(RfpTSH.java:497)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.
    spiNotify(RemoteFAP.java:3992)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.
    jmqiNotify(RemoteFAP.java:3853 )
    at
    com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.
    setRunning(WMQSync ConsumerShadow.java:440)
    at
    com.ibm.msg.client.wmq.internal.WMQMessageConsumer.
    stop(WMQMessageConsumer.java:522)
    at
    com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.
    stopUnconditional (JmsMessageConsumerImpl.java:646)
    at
    com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.
    stop(JmsMessageConsumerImpl.java:666)
    at
    com.ibm.msg.client.jms.internal.JmsSessionImpl.
    stop(JmsSessionImpl.java: 2002)
    at
    com.ibm.msg.client.jms.internal.JmsSessionImpl.
    stop(JmsSessionImpl.java: 1967)
    at
    com.ibm.msg.client.jms.internal.JmsConnectionImpl.
    stop(JmsConnectionImpl.java:818)
    at
    com.ibm.mq.jms.MQConnection.stop(MQConnection.java:471)
    at TestStop.main(TestStop.java:104)
    ----------------------------------------------------------------
    
    Failure 2:
    ----------------------------------------------------------------
    
    javax.transaction.xa.XAException: The method 'xa_commit' has
    failed with errorCode '-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.commit(JmqiXAResource.java:407)
    at TestStop$1.run(TestStop.java:81)
    javax.transaction.xa.XAException: The method 'xa_start' has
    failed with errorCode '-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.start(JmqiXAResource.java:802)
    at TestStop$1.run(TestStop.java:77)
    javax.transaction.xa.XAException: The method 'xa_end' has
    failed with errorCode'-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.end(JmqiXAResource.java:457)
    at TestStop$1.run(TestStop.java:80)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of multi-threaded applications that use
    the WebSphere MQ v7 classes for Java Message Service (JMS)
    which issue a:
    
    Connection.stop();
    
    method call to temporarily suspend the receiving of messages on
    a JMS Connection object.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    When a multi-threaded application issues the JMS method call:
    
    Connection.stop();
    
    to halt the receiving of messages across the connection,
    exception messages and FFDCs can be produced if there are
    threads actively requesting messages from the queue manager at
    the time of the stop() method call.
    
    These include:
    ================================================================
    java.lang.NullPointerException
    at
    com.ibm.mq.jmqi.remote.internal.system.RfpTSH
    .setControlFlags1(RfpTSH.java:497)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.
    spiNotify(RemoteFAP.java:3992)
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.
    jmqiNotify(RemoteFAP.java:3853)
    ... ... ...
    
    ===========================================================
    javax.transaction.xa.XAException: The method 'xa_commit' has
    failed with errorCode '-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.commit(JmqiXAResource.java:407)
    at TestStop$1.run(TestStop.java:81)
    
    ============================================================
    javax.transaction.xa.XAException: The method 'xa_start' has
    failed with errorCode '-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.start(JmqiXAResource.java:802)
    at TestStop$1.run(TestStop.java:77)
    
    ============================================================
    javax.transaction.xa.XAException: The method 'xa_end' has
    failed  with errorCode '-3'.
    at
    com.ibm.mq.jmqi.JmqiXAResource.end(JmqiXAResource.java:457)
    at TestStop$1.run(TestStop.java:80)
    
    =============================================================
    

Problem conclusion

  • This problem was associated with the multiple threads
    interfering with each other when this operation is called.  A
    code change was made to resolve the issue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    Windows            U200320
    AIX                U834987
    HP-UX (PA-RISC)    U834414
    HP-UX (Itanium)    U834413
    Solaris (SPARC)    U834986
    Solaris (x86-64)   U834210
    iSeries            tbc_p700_0_1_3
    Linux (x86)        U834415
    Linux (x86-64)     U834985
    Linux (zSeries)    U834412
    Linux (Power)      U835662
    
    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

    IC68653

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-14

  • Closed date

    2010-05-27

  • Last modified date

    2010-05-27

  • 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

[{"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","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 May 2010