APAR status
Closed as program error.
Error description
The webserver/plugin is opening a connection to the app server,
sending the extended handshake msg to the http transport, and
then closing the connection after it receiveds an HTTP OK
response. This causes an exception to occur in the HTTP Trans-
port while trying to read the request. There is an error in the
transport in that it should immediately halt processing on the
connection, but it does not do that. Instead it hands the NULL
request off to the servlet engine to handle and that leads to
the PLGN007 error.
Local fix
N/A
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of the *
* Extended Handshake feature for the plugin. *
****************************************************************
* PROBLEM DESCRIPTION: An "OSEListenerDi E PLGN0007E: Engine *
* Throwable" error can be seen if the *
* plugin does not send a valid request *
* within the connection time out *
* period after sending an Extended *
* Handshake request. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The plugin sends an "Extended Handshake" request to the
Application Server to check if it is alive.
HttpConnection.readAndHandleRequest() responds to the request
and then invokes HttpRequest.readRequest() to read the real
request, which it assumes will be sent next. If a request is
not received within the time out period,
HttpRequest.readRequest() returns an error code to
HttpConnection.readAndHandleRequest().
The "Extended Handshake" processing fails to check for an
error from HttpRequest.readRequest and calls the engine code
to handle the request. Since no request had been received, the
request information is NULL and the engine will encounter the
PLGN007 error.
Problem conclusion
HttpConnection.readAndHandleRequest() had been changed to treat
the Extended Handshake as a separate request. This allows the
normal KeepAlive processing to handle the process of waiting
for the next request and handling a time out if no request is
sent.
The fix for this problem is currently targetted for inclusion
in service pack 5.0.2.10 & 5.1.1.4.
Please refer to the Recommended Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ96915 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-11-08 |
Closed date |
2005-01-03 |
Last modified date |
2005-01-03 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|