Troubleshooting
Problem
Client POST Requests from User-Agent: Java1.6.0.02 client may intermittently fail due to a previous idle keep alive connection being closed by the IBM HTTP Server. It is normal for the web server to close an idle keep alive connection after KeepAliveTimeout fires (default 15 seconds). It is not normal behavior for a client to send an HTTP request over a previously closed connection. The Java client may eventually retry the same POST request again over a new connection, but the retried request fails because the request is missing the POST body data.
Symptom
[23/Feb/2012:16:35:30 +0530] "POST /example HTTP/1.1" 200 -
If Loglevel="Trace" is enabled in the plugin-cfg.xml, the http_plugin.log will typically report the following message indicating it failed to read the body data as well
[Thu Feb 23 16:43:29 2012] 00000289 00000004 - TRACE: mod_was_ap20_http:
cb_read_body: Failed to read the full body from the browser. just_read =
0 of the expected 2677
[Thu Feb 23 16:43:29 2012] 00000289 00000004 - TRACE: lib_htrequest:
htrequestSetError: Setting the error to: |READ_FAILED|(1, Line: 1625)
[Thu Feb 23 16:43:29 2012] 00000289 00000004 - WARNING: ws_common:
websphereExecute: Error reading post data from client
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21590497