PI18962: THE REMAINING REQUEST BODY IS PURGED AFTER THE REQUEST IS COMPLETED

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The remaining request body is purged after the request is
  completed
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The channel does not stop reading the   *
  *                      request data from a socket that has     *
  *                      been set to close and waits until all   *
  *                      the data is read                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the HTTP Channel is closing the connection (either at the
  end of a request/response or there was an exception during
  request processing) it will detect if all the request data has
  been read. If it has not, then the channel will attempt to read
  all the data from the socket so it can reuse the connection.
  This means that if there is a large amount of data left that
  the
  channel will have to read it all in, which could prevent other
  work from being executed in a timely manner. The channel has to
  read the data off the socket if it's going to leave the socket
  open to read for another request, otherwise it will read the
  stale data and encounter an exception.
  

Problem conclusion

• The HTTP Channel will now prevent the request body from being
  purged off the wire if we detect it hasn't been fully read and
  the request is not persistent.
  
  A new custom property was added to the HTTP Channel to enable
  this new behavior. The property name is:
  "preventRequestBodyPurge" with a possible value of "true" or
  "false", with the default being "false".
  
  An HTTP Channel custom property can be set like this:
  
  http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.0.0/com.i
  bm.websphere.nd.multiplatform.doc/info/ae/ae/rrun_chain_httpcust
  om.html?cp=SSAW57_8.0.0%2F3-16-5-416&lang=en
  
  Please note: the instructions are for v8.0, but the same
  instructions apply to all versions of WebSphere Application
  Server Full Profile.
  
  This custom property must be enabled if the Web Container
  Custom Property
  "com.ibm.ws.webcontainer.skipinputstreamreadonerror" is in
  use. If there is any exception during the process of the POST
  data, the Web Container property will stop reading in the
  remaining unread data.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.4.  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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP