PQ86603: IBM HTTP Server V2.0.x
mod_alias/mod_rewrite conflict with V5.0 plug-in
Downloadable files
Abstract
WebSphere® Application Server V5.0 plug-in shipped with
V5.0.2.5 conflicts with IBM® HTTP Server V2.0.x. This plug-in replacement
is compatible with IBM HTTP Server V2.0.x.
Download Description
WebSphere Application Server component plug-in fix is a native code
module that runs as a plug-in in the web server. It can be independently
installed on a Web server in a WebSphere Application Server configuration.
Review Web server plug-in policy for more details.
Additional defects since 5.0.2.5 included in this component plug-in
fix
PQ84887 - Plug-in did not do failover correctly
PQ86467 - iPlanet plug-in failed to parse and set headers
PQ86603 - Plug-in conflict with IBM HTTP Server 2.0.x MOD_ALIAS and
MOD_REWRITE modules
The README file that is shipped with this component plug-in fix includes
additional details about these fixes and other important information.
Superseded fixes
WebSphere Application Server Service Pack 5.0.2.5 plug-in
WebSphere Application Server Service Pack 5.0.2.4 plug-in
WebSphere Application Server Service Pack 5.0.2.3 plug-in
WebSphere Application Server Service Pack 5.0.2.2 plug-in
WebSphere Application Server Service Pack 5.0.2.1 plug-in
Cumulative plug-in fix WAS_Plugin_11-19-2003_5.0.X_cumulative_Fix
Cumulative plug-in fix WAS_Plugin_09-03-2003_5.0.X_cumulative_Fix
Cumulative plug-in fix WAS_Plugin_07-14-2003_5.0.X_cumulative_Fix
Cumulative plug-in fix WAS_Plugin_07-01-2003_5.0.X_cumulative_Fix
Cumulative plug-in fix WAS_Plugin_06-23-2003_5.0.X_cumulative_Fix
Cumulative plug-in fix WAS_Plugin_04-23-2003_5.0.X_cumulative_Fix
All plug-in defects reported by April 12, 2004 are included in this fix. F
RECOMMENDED fixes for the Application Server side of a WebSphere
Application Server configuration
Apply this plug-in fix if you experience any problems with WebSphere
Application Server V5.0 plug-in before contacting IBM Software Support.
This interim fix applies to the Web server side of a WebSphere Application
Server configuration.
Notice for WebSphere Portal Server V4.x users
All WebSphere Portal Server V4.x configurations that include the WebSphere
Application Server V5.0 plug-in should apply the WebSphere Application
Server V5.0 component plug-in fix, or any later V5.0 plug-in included in a
WebSphere Application Server V5.0 fix pack or cumulative fix that
supersedes cumulative component plug-in fix.
Do not apply WebSphere Application Server 4.0 cumulative component plug-in
fix to WebSphere Portal Server V4.x configurations. WebSphere Portal
Server 4.x users must apply the WebSphere Application Server V5.0
component plug-in fix manually by following instructions that are listed
at the end of this document.
Performance tuning considerations
Consider increasing several default HTTP transport parameters of WebSphere
Application Server Web container to prevent premature I/O & KeepAlive
timeout of http requests, especially when the Web server is remote and
connection between the client and Web Server are slow, such as when the
client is using a modem connection or the HTTP requests use POST:
Increased number of InterruptedException (Read timed out) exceptions
may be observed in the Application Server logs after PQ70037 is installed,
which is included also in this cumulative plug-in fix.
Each system is unique and has different optimum parameter settings.
These are reasonable values for Web container settings to start with:
ConnectionKeepAliveTimeout = 10 - 60 (default is 5)
ConnectionIOTimeout = 10 - 60 (default is 5)
In WebSphere Application Server 5.0.1, ConnectionKeepAliveTimeout &
ConnectionIOTimeout settings are in milliseconds. In WebSphere Application
Server 5.0, 5.0.2 & later, ConnectionKeepAliveTimeout &
ConnectionIOTimeout settings are in seconds.
General recommendation is to set ConnectionIOTimeout and
ConnectionKeepAliveTimeout to the same or lower values as their
corresponding parameters in Web server, such as Timeout and
KeepAliveTimeout in IBM HTTP Server or Apache. Results of performance
tests should show optimum parameters for HTTP transport of the Servlet
Engine.
Use WebSphere JDK when you run UpdateInstaller to install this fix
(for example run setupCmdLine.sh script)
Run updateWizard/updateSilent script from the Updateinstaller root
folder as a root/Administrator
Here is the example of a silent installation of this component plug-in fix
on Windows:
updateSilent -fix -install -fixdir C:\temp\WebSphere\fix -installdir
C:\WebSphere50\AppServer -fixes WAS_Plugin_04-12-2004_5.0.X_cumulative
Also,
The WebSphere Application Server plug-in module is installed on the
supported Web server that meets minimum software prerequisites, including
minimum hardware and software prerequisites.
The minimum Global Security Kit (GSKIT) level that is required by the
WebSphere Application Server plug-in for SSL communication with WebSphere
Application Server, installed on a Web server.
The WebSphere Application Server V5.0 plug-in component can be
installed and maintained independently of fix packs or cumulative fixes.
Installing the latest plug-in modules can eliminate an existing
problem with very low risk of impacting the Application Server processes.
This component specific fix supersedes any plug-in fixes previously
installed, through WebSphere Application Server V5.0.2.5. Future fix packs
and cumulative fixes will supersede this fix.
Manual installation
You can install this component plug-in fix manually in a case that you
experience any problems to install it interactively or silently by using
UpdateInstaller tool.
Please refer to the readme for detailed installation instructions