APAR status
Closed as program error.
Error description
Application server threads and plugin threads hang
because both sides are waiting on a read(), expecting
data from the other side. The result is that new
requests are not serviced.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 4.0 users *
****************************************************************
* PROBLEM DESCRIPTION: GET requests with content fail because *
* the plugin is not forwarding the *
* request content to the application *
* server. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The plugin only expects request content on POST and PUT
requests, therefore it would not request the content from the
client. The GET requests containing a content-length header
would cause the transport to block, waiting on content that
never comes. The HTTP 1.1 spec does not rule out content on a
GET request.
Problem conclusion
Added configurable option AcceptAllContent to allow request
content for all types of request (for example, POST, PUT, GET,
and HEAD).
The default behavior is to allow content for POST and PUT
requests only.
To enable this feature, the plugin-cfg.xml file must be
updated to contain the AcceptAllContent attribute.
Example:
<Config AcceptAllContent="True">
The default value for AcceptAllContent is false.
Temporary fix Comments
APAR information |
APAR number |
PQ76729 |
Reported component name |
WEBSPHERE AE NT |
Reported component ID |
5630A2201 |
Reported release |
400 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Submitted date |
2003-07-24 |
Closed date |
2003-08-28 |
Last modified date |
2003-08-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SRLS
Applicable component levels |
R400 PSY |
UP |
|