IBM Support

IV97412: IBM MQ 8.0 XMS APPLICATION THROWS NULLREFERENCEEXCEPTION WHILE RECONNECTING TO WAS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • XMS.NET application crashes with NullReferenceException while
    reconnecting to WAS, if multiple end points are provided.
    Following is the exception that is thrown.
    
    Linked Exception :
    IBM.XMS.SIB.JFAP.JFAPConnectionBrokenException:
    Invalidate() ---> System.NullReferenceException: Object
    reference not
    set to an instance of an object.
       at IBM.XMS.Comms.IoRequest.DispatchRequestCompleteCallback()
       at IBM.XMS.Comms.IoRequest.IoCompleteInternal(Int32
    bytesTransferred, Exception ex)
       at IBM.XMS.Comms.IoRequest.IoCompleteCallback(IAsyncResult
    ar)
       at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
       at
    System.Net.ContextAwareResult.CaptureOrComplete(ExecutionContext
    &
    cachedContext, Boolean returnContext)
       at System.Net.ContextAwareResult.FinishPostingAsyncOp
    (CallbackClosure& closure)
       at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32
    offset,
    Int32 size, SocketFlags socketFlags, SocketError& errorCode,
    AsyncCallback callback, Object state)
       at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32
    offset,
    Int32 size, SocketFlags socketFlags, AsyncCallback callback,
    Object
    state)
       at
    IBM.XMS.Comms.TcpSocket.IBM.XMS.Comms.ISocket.BeginSend(Byte[] ,
    Int32 , Int32 , SocketFlags , AsyncCallback , Object )
       at IBM.XMS.Comms.Channels.SocketBasedChannel.BeginSend(Byte[]
    buffer, Int32 offset, Int32 count, AsyncCallback callback,
    Object state)
       at IBM.XMS.Comms.IoRequest.StartIo()
       --- End of inner exception stack trace ---
       at
    IBM.XMS.SIB.JFAP.ConversationImpl.RequestReplyExchange(IByteBuff
    er
    [] data, JFAPSegmentType segmentType, UInt16 requestNumber,
    IoPriority
    priority, Boolean pooledBufferHint)
       at IBM.XMS.SIB.JFAP.ConversationImpl.RequestReplyExchange
    (IByteBuffer data, JFAPSegmentType segmentType, UInt16
    requestNumber,
    IoPriority priority, Boolean pooledBufferHint)
       at
    IBM.XMS.SIB.Comms.Client.JFAPCommunicator.RequestReplyExchange
    (IByteBuffer data, JFAPSegmentType sendSegType, MessagePriority
    priority, Boolean canPoolOnReceive)
       at IBM.XMS.SIB.Comms.Client.ConsumerSessionProxy.Stop()
       at IBM.XMS.Impl.MsgConsumer.Stop()
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS.NET APPLICATIONS USING MULTIPLE PROVIDER ENDPOINTS WHILE
    CONNECTING TO WAS
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If multiple provider endpoints are provided while establishing a
    connection to WAS, XMS application fails during reconnection and
    intermittently crashes will NullReferenceException
    

Problem conclusion

  • If multiple provider end points are set while establishing a
    connection to WAS,if connection to the first end point breaks,
    XMS application should try re-connecting to the secondary end
    point.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.3
    
    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

    IV97412

  • Reported component name

    WMQ XMS V 8.0

  • Reported component ID

    5724H7257

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-22

  • Closed date

    2017-07-28

  • Last modified date

    2017-08-07

  • 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 XMS V 8.0

  • Fixed component ID

    5724H7257

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 August 2017