PM44033: JAX-WS applications on Feature Pack for Web Services 6.1.0.37 might malfunction when webservices trace is enabled.

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47

APAR status

• Closed as program error.

Error description

• After applying 6.1.0.37, a JAX-WS client might incorrectly send
  a document/literal/wrapped message, when its WSDL describes
  the message as bare.
  
  For example, before 6.1.0.37, the following request message is
  sent across the wire:
  
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  ...>
     <soapenv:Header/>
     <soapenv:Body>
        <p123:HelloRequest>
         ...
  
  After upgrading to 6.1.0.37, the same JAX-WS client might send
  the following request:
  
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  ...>
     <soapenv:Header/>
     <soapenv:Body>
        <p123:SayHello>
         ...
  
  Most likely, the receiving service would not be able to
  consume this request message, since the message is
  incorrectly marshalled as wrapped, versus bare.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  Feature Pack for Web Services JAX-WS        *
  *                  applications.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Upgrading to Feature Pack for Web       *
  *                      Services 6.1.0.37 might break           *
  *                      previously working JAX-WS applications  *
  *                      if trace is running.                    *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack that includes this       *
  *                  APAR.                                       *
  ****************************************************************
  After applying 6.1.0.37, a JAX-WS client might incorrectly send
  a document/literal/wrapped message, when its WSDL describes
  the message as bare.
  For example, before 6.1.0.37, the following request message is
  sent across the wire:
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  ...>
  <soapenv:Header/>
  <soapenv:Body>
  <p123:HelloRequest>
  ...
  After upgrading to 6.1.0.37, the same JAX-WS client might send
  the following request:
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  ...>
  <soapenv:Header/>
  <soapenv:Body>
  <p123:SayHello>
  ...
  Most likely, the receiving service would not be able to
  consume this request message, since the message is
  incorrectly marshalled.
  Likewise, if a JAX-WS service is running on the upgraded
  system, a javax.xml.bind.UnmarshalException might occur when
  it tries to demarshal the request message.
  

Problem conclusion

• This error is caused by the logging of an internal JAX-WS
  engine object, added under PM23191. This APAR changes
  how this logging is done so that the error no longer happens.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.41.  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM44237

Fix information

• Fixed component name

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP