APAR status
Closed as program error.
Error description
When custom error pages defined on the IIS webserver, WebSphere
plugin is not sending the custom error page to the client incase
of failure.
Local fix
N/A
Problem summary
****************************************************************
* USERS AFFECTED: WebSpher Application Server 5.0/5.1 plugins *
* users of IIS 5.x *
****************************************************************
* PROBLEM DESCRIPTION: IIS/plugin closes a client connection *
* without sending an error page. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
IIS webserver terminates connection to client without sending
any error message. When Application Server IIS plugin could not
connect to the Application Server, it returns error code to IIS.
However it is the plugin's responsibility to return an error
page to the browsers before returning error status to IIS.
Problem conclusion
The fix provides a way to set the customized error page
location for Application Server IIS plug-in and if the error
pages exists, the plug-in will return these error pages to the
browsers before returning an error code to IIS.
Warning: Please get help from your computer administrator
or a Microsoft consultant if you are not familiar with regedit
tool. Using regedit incorrectly can cause serious problems
that may require you to reinstall your windows operating
system. IBM cannot guarantee that problems resulting from
the incorrect use of Registry Editor can be solved. Use
regedit at your own risk.
To define the error page location in registry, please follow
these steps:
1. start regedit.exe, the registry editor.
2. right-click following key:
"HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application
Server\version"
where, version is your WAS server version, such as 5.0.0.0.
If you could not find above key, please ask an IBM consultant
near you.
3. Follow the popup-menu: new -> String value, and fill in
with "IIS Error Location" in the name field, press "Enter" key.
4. right-click the "IIS Error Location", then select modify.
After
filling in the directory in the "value data" part, click ok. The
directory you entered must contain the error page files that
you want plug-in sending to client browsers.
The error page file name must have following format:
xxx.htm, where xxx is the HTTP code. Currently only 500,
503, 413 HTTP error codes are used by WAS plug-in.
Example, assuming above "IIS Error Location" has the value:
"C:\WINNT\Help\iisHELP\Common"
and plug-in gets the internal server error 500. The plug-in
will try to open following file:
"C:\WINNT\Help\iisHELP\Common\500.htm"
If that directory and the error page file do exist, plug-in
will return HTTP error code 500 with the content of above error
page file to client browser before it returns the error code
to IIS.
Temporary fix Comments
APAR information |
APAR number |
PQ85348 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-01 |
Closed date |
2004-05-10 |
Last modified date |
2004-05-10 |
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 |
R00W PSY |
UP |
R10W PSY |
UP |
|