JR36471: CMVC 200047 - PREVENT AN EMPTY RESPONSE OBJECT FOR A WEB SERVICE RESPONSE WHEN CONTENT-LENGTH HEADER IS NOT PRESENT

7.0.0-WS-WCServer-FP009
WebSphere Commerce Version 7.0.0.2 Fix Pack
WebSphere Commerce Version 7.0.0.4 Fix Pack
WebSphere Commerce Version 7.0.0.3 Fix Pack
WebSphere Commerce Version 7.0.0.5 Fix Pack
WebSphere Commerce Version 7.0.0.6 Fix Pack
WebSphere Commerce Version 7.0.0.7 Fix Pack
WebSphere Commerce Version 7.0.0.8 Fix Pack
WebSphere Commerce Version 7.0.0.9 Fix Pack

APAR status

• Closed as program error.

Error description

• You are using IBM WebSphere Commerce web services.
  Intermittently you are getting empty responses that could lead
  to NullPointerExceptions.
  
  The problem is related to the way WebSphere Commerce handles the
  response from other systems. When this interim fix is not
  applied, if the content-length header is missing then WebSphere
  Commerce could think the response is complete before the body is
  processed, therefore generating an empty response object.
  
  Note that this interim fix includes JR34672 which was created to
  update the adapter to respect the content length header of the
  response. JR34672 also addresses empty responses but for the
  cases when the content-length is set in the header.
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce 6 Feature Pack 1 and WebSphere Commerce 7
  users which are using the WebSphere Commerce Web Service
  adaptors.
  
  PROBLEM ABSTRACT:
  Empty response object for a web service response when the
  content-length header is not present in WebSphere Commerce.
  
  BUSINESS IMPACT:
  The web service can fail Intermittently, making the
  functionaility provided by it unavailable.
  
  RECOMMENDATION:
  

Problem conclusion

• To resolve this issue, the Web Service adapter code was changed
  to correctly parse Web Service responses when the content-length
  header is not present
  
  In order to enable the fix provided for this APAR, additional
  steps are required which are also described in the readme file
  included in the Interim Fix package:
  
  To enable the fix for a particular message type, follow these
  instructions:
  
  1. Edit the WebSphere Commerce configuration file and Locate the
  InteractionSpec node for this class:
  com.ibm.commerce.wc.messaging.adapters.jcahttp.ws.JCAHTTPWSInter
  actionSpecImpl
     and add the following EditableProperty:
  
  <EditableProperty Admin="bufferResponse"
  display="false" editable="yes"
  name="setIsBufferResponse" value="false"/>
  
  2. Propagate the change to the WebSphere Commerce configuration
  file
  3. Ensure the JVM is restarted and the interim fix is applied
  
  Configure the message to use the bufferResponse property.
  
  1. Open the WebSphere Commerce Administration Console
  2. Select Configuration -> Message Types
  3. Open the message
  4. Click Next
  5. In the Change Message Transport Assignment panel, set
  bufferResponse to true
  
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

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:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R600 PSY

     UP

• R700 PSY

     UP