IBM Support

PI22569: MQ RFH2 HEADER IS PROPAGATED EVEN THOUGH IT IS DISABLED AT THE DESTINATION.

Fixes are available

8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • MQ RFH2 header is propagated even though it is disabled at  the
    destination.
    Customer sends multiple messages in a single transaction. If
    the first message is sent from a destination with
    enabledRFH2Header set to 'true', all subsequent messages sent
    from destinations with enableRFH2Header set to 'false' will
    have an RFH2 header.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: In an environment where MQ queue        *
    *                      manager is added as a bus member,       *
    *                      eventhough RFH2 propagation is          *
    *                      disabled on the SIB destination which   *
    *                      corresponds to the MQ destination,      *
    *                      the MQ RFH2 headers are still           *
    *                      propagated. When propagation is         *
    *                      disabled, SIB should not attempt to     *
    *                      propogate the RFH2 headers.             *
    ****************************************************************
    * RECOMMENDATION:  None                                        *
    ****************************************************************
    It is found that under a single transaction, when messages are
    sent to more than one SIB MQ destinations, if for the first
    destination the MQ RFH2 propagation is disabled, the MQ RFH2
    headers are propagated to all other destinations involved in
    the transaction. This is irrespective of whether this property
    is enabled or disabled on the other destinations.
    When the RMQSession object is created for the transaction, the
    enableRFH2Header value is set in it by reading the value from
    the configuration of first SIB destination. This same value is
    used further when the messages are sent to other destinations
    in the same transaction.
    

Problem conclusion

  • Code changes have been made to read the enableRFH2Header
    value from the corresponding MQLocalizationPoint rather than
    from the RMQSession object.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.5, 8.0.0.10 and 7.0.0.37 .  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI22569

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-23

  • Closed date

    2014-10-13

  • Last modified date

    2014-10-13

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 8.0

Reference #: PI22569

Modified date: 13 October 2014