IBM Support

PI77841: DELIVERYDELAY PROPERTY IS NOT SET WHEN A MESSAGE IS RECEIVED THROUGH THE MQLINK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On WAS 9 the channel in the z/OS QMGR can be started, if there
    are no messages in the z/OS queue. But when messages will be put
    into the queue they will be moved to the transmission queue and
    the channel changes to "retry".
    
    The Error message is:
    PersistentDataEncodingException: CWSIP0262E: The current message
     is
    corrupt and can not be added to the persistent store due to
    exception
    com.ibm.ws.sib.mfp.MessageEncodeFailedException:
    com.ibm.ws.sib.mfp.jmf.
    JMFUninitializedAccessException: deliveryDelay
    ...
    Caused by: com.ibm.ws.sib.mfp.MessageEncodeFailedException:
    com.ibm.ws.
    sib.mfp.jmf.JMFUninitializedAccessException: deliveryDelay
            at
    com.ibm.ws.sib.mfp.impl.JsMsgObject.encodePart(JsMsgObject.
    java:1382)
    
    
    This is related to the fact that a value for the deliveryDelay
    property is only set during a SIB send operation, which
    effectively does not occur when a message is received through
    the MQLink and then converted into SIB message format.
    
    While testing this locally, it turns out there is a similar
    issue with the jmsDeliveryTime property (another JMS property
    that was introduced as part of JMS2.0), and this was being
    obscured by the deliveryDelay problem being encountered first.
    
    This iFix will fix the problem for both properties.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the MQLink to receive          *
    *                  messages from IBM MQ                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messages cannot be sent from IBM MQ to  *
    *                      IBM WebSphere Application Server V9     *
    *                      using the MQLink.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    MQ Messages being sent via MQLink to a V9 SIBus destination
    might stay on the MQ transmission queue with the channel
    remaining in "retry" state.
    The application server log might show an exception similar to:
    PersistentDataEncodingException: CWSIP0262E: The current
    message
    is
    corrupt and can not be added to the persistent store due to
    exception
    com.ibm.ws.sib.mfp.MessageEncodeFailedException:
    com.ibm.ws.sib.mfp.jmf.
    JMFUninitializedAccessException: deliveryDelay
    ...
    Caused by: com.ibm.ws.sib.mfp.MessageEncodeFailedException:
    com.ibm.ws.
    sib.mfp.jmf.JMFUninitializedAccessException: deliveryDelay
    at
    com.ibm.ws.sib.mfp.impl.JsMsgObject.encodePart(JsMsgObject.
    java:1382)
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI77841

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-09

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021