IBM Support

PH03014: A PROPERTY IS SET IN THE REQUESTCONTEXT, BUT THE INTERCEPTOR DOES NOT READ THIS PROPERTY RESULTING IN A NULLPOINTEREXCEPTI

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using "cxf.add.attachments = true" in the MessageContext
    works
    fine but for one specific usecase where it does not work:
    When using Dispatch-API, you can only access the
    RequestContext. So they tried to define the property this
    way:
    
    BindingProvider bp = (BindingProvider) _proxy;
    bp.getRequestContext().put("cxf.add.attachments",
    Boolean.TRUE);
    
    The property is set in the RequestContext, but the
    interceptor
    does not read this property and results in a
    NullPointerException
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
    *                  users of JAX-WS Web Services                *
    ****************************************************************
    * PROBLEM DESCRIPTION: SOAP attachments in a Web service       *
    *                      request were not processed by Web       *
    *                      services CXF code                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Some types of binary attachments sent in a Web Services SOAP
    request were not processed by the Web services CXF code in
    Liberty.  The CXF code only processed MTOM attachments in the
    SOAP request.
    

Problem conclusion

  • The CXF attachment interceptors did not recognize attachments
    sent in a SOAP request that were not MTOM attachments. This
    problem was resolved by adding a custom property
    "cxf.add.attachments" that needs to be set in the request
    context of the SOAP message.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.4.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • There is no work around available for this problem.
    

Comments

APAR Information

  • APAR number

    PH03014

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-19

  • Closed date

    2018-10-25

  • Last modified date

    2018-10-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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

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

Document Information

Modified date:
17 October 2021