IBM Support

PM25126: The message edited by a JAX-WS outbound client handler disappears if one of the JAX-WS handlers returns false.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Background:
    All JAX-WS handlers have a handleMessage method which you
    may use to query and change the XML message.
    If a JAX-WS handleMessage method returns false, the handler
    chain is reversed.
    
    For example, if a JAX-WS client outbound handler returns false
    the following occurs:
    A) The handler chain is reversed.
    B) The outbound message becomes the inbound message.
    C) The handlers that were previously called for outbound
    processing are called for inbound processing.
    D) Flow of control returns to the customer's JAX-WS
    BindingProvider (Dispatch or Proxy)
    
    
    Problem:
    In some cases, the (B) processing fails.  The outbound message
    is lost and a different message is used for the inbound
    processing.   The result is unexpected behavior when the flow
    of control returns to the customer's JAX-WS BindingProvider (D).
    
    Important Note:
    Most customer handlers will not return false.  This scenario
    is most common if you are writing a test application to
    simulate a web service invocation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
    *                  of JAX-WS handlers                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: The message edited by a JAX-WS          *
    *                      outbound client handler disappears if   *
    *                      one of the JAX-WS handlers returns      *
    *                      false.                                  *
    ****************************************************************
    * RECOMMENDATION:  Install an fix pack containing this APAR    *
    ****************************************************************
    Background:
    All JAX-WS handlers have a handleMessage method which you
    may use to query and change the XML message.
    If a JAX-WS handleMessage method returns false, the handler
    chain is reversed.
    
    For example if a JAX-WS client outbound handler returns false
    the following occurs:
       A) The handler chain is reversed.
       B) The outbound message becomes the inbound message.
       C) The handlers that were previously called for outbound
    processing are called for inbound processing.
       D) Flow of control returns to the customer's JAX-WS
    BindingProvider (Dispatch or Proxy)
    
    
    Problem:
    In some cases, the (B) processing fails.  The outbound message
    is lost and a different message is used for the inbound
    processing.   The result is unexpected behavior when the flow
    of control returns to the customer's JAX-WS BindingProvider (D).
    
    Important Note:
    Most customer handlers will not return false.  This scenario
    is most common if you are writing a test application to
    simulate a web service invocation.
    

Problem conclusion

  • When a JAX-WS handler edits the XML message, the JAX-WS
    runtime stores this message for subsequent handler calls.
    However the handler chain reversal algorithm did not use this
    edit XML message for the inbound message.   Instead it used a
    stale (pre-edited) copy of the outbound message.
    
    The JAX-WS runtime is changed to correctly use the edited XML
    message when the handler chain is reversed
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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

    PM25126

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-25

  • Closed date

    2010-11-10

  • Last modified date

    2011-07-25

  • 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

  • R700 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":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 October 2021