IBM Support

IT08646: IF THE EXPIRY VALUE IS INVALID FOR A REPLY MESSAGE, THE POISON MESSAGE IS NOT WRITTEN TO THE REPLY OR BACKOUT QUEUE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A .NET WCF client is calling a WCF server using the WebSphere MQ
    custom channel for WCF. The client is configured to use a
    request/reply queue pair of a Queue-Manager.
    
    When a reply message is detected the utility RFHUtil
    modifies the MQMD expiry value of the request message in-flight.
    
    When the reply message is about to be written to the reply queue
     the JMS time to live property is found to be invalid (due to a
    large negative value).
    
    CWSMQ00007E: The specified value {1} is not allowed for
    {0}.XMSC_INSERT_VALUE-1426770377263XMSC_INSERT_TYPEJmsTimeToLive
    The given value is not allowed for the property specified.
    Change the value to a value that is supported for the property.
    
    However, the poison message is not written to the backout queue
    due to a failed validation of the JMS DeliveryMode property.
    
    The XMS log file shows:
    
    00000011 X UOW=
    source=IBM.XMS.Client.WMQ.WmqPoison org=IBM prod=WebSphere
    component=Message Service Client for .NET thread=[1 : 0]
    IBM.XMS.XMSException: CWSMQ0123E: The property name deliveryMode
    is not valid to be set to 00000003.
    The Value is not valid for the property.
    Check the property name value are correct.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All WCF Applications using Poison Message Handling
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
     When a WCF RequestReply client puts a message onto the request
    queue, the message 's MQMD property has been modified using the
    RFHUtil tool and the message is put back onto the queue.The
    message is treated as poison message and during poison message
    handling the following exception is thrown.
      [24-03-2015 22:03:08:214075 W. Europe Standard Time] 00000011
    X UOW= source=IBM.XMS.Client.WMQ.WmqPoison org=IBM
    prod=WebSphere component=Message Service Client for .NET
    thread=[1 : 0]
     IBM.XMS.XMSException: CWSMQ0123E: The property name
    deliveryMode is not valid to be set to 00000003.
     The Value is not valid for the property.
     Check the property name value are correct.
     at IBM.XMS.Client.WMQ.WmqSendMarshal.ConstructMQMD()
     at IBM.XMS.Client.WMQ.WmqSendMarshal.ExportMQMD()
     at IBM.XMS.Client.WMQ.PoisonMessage.CalculateMqmdAndBuffers()
     at IBM.XMS.Client.WMQ.PoisonMessage.get_MQMD()
     at IBM.XMS.Client.WMQ.WmqPoison.Put(PoisonMessage pmsg, String
    destname, String qmname, Boolean newMsgId)
     at IBM.XMS.Client.WMQ.WmqPoison.BackoutRequeue(PoisonMessage
    pmsg)
    

Problem conclusion

  • During the Poison Message handling phase of WCF the delivery
    mode of the message is set to a invalid value.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.8
    v8.0       8.0.0.4
    
    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

    IT08646

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-04

  • Closed date

    2015-06-30

  • Last modified date

    2017-05-02

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7251

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.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 May 2017