This is a component cumulative fix for the WebSphere®
Application Server V 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6 and 4.0.7 plug-in
as of 16 September 2004.
Download Description
These are new defects that were fixed in this cumulative plug-in fix
in addition to all previous fix packs and WebSphere Application Server
component cumulative plug-in fixes:
PQ88879
- Plug-in returned success code while failed to load new plugin-cfg.xml
PQ89583
- Plug-in marked the appserver down incorrectly
PQ92641
- Apache plug-in did not send the client SSL certificate
PQ93112
- Unclosed Connections caused plug-in performance degradation
The README file that is shipped with this cumulative plug-in fix includes
additional details about these fixes and other important information.
RECOMMENDED fixes for the Application Server side of a WebSphere
Application Server configuration
PQ70895
- Web container attempts to read POST data after IO Time-out (This fix is
needed only for WebSphere Application Server V4.0.4-4.0.5).
PQ70205
- WebSphere Application Server fails to handle POST requests when the POST
data is sent in time intervals greater than the connection time-out (This
fix is needed only for WebSphere Application Server V4.0.2-4.0.5).
PQ69608
- The plug-in is failing over as expected when a proxy firewall is between
the plug-in and the Application Server (This fix is needed only for
WebSphere Application Server V4.0.2-4.0.5).
Apply this plug-in fix if you experience any problems with WebSphere
Application Server V4.0 plug-in before contacting IBM Software Support.
This interim fix applies to the Web server side of a WebSphere Application
Server configuration.
Important notes about plug-in behavior
In the WebSphere Application Server V4.0.2-4.0.4 plug-in, the
VirtualHost matching is performed against the receiving port in the Web
server process.
In the WebSphere Application Server V4.0.5 and later, the VirtualHost
matching is performed against the port that is parsed from the host
header. This behavior fully complies with HTTP 1.1 specification.
This component cumulative plug-in fix supersedes the WebSphere
Application Server V4.0.7 plug-in. In other words, installing this
component cumulative plug-in fix on top of WebSphere Application Server
V4.0.2 through V4.0.4, the plug-in matching behavior will change.
To maintain the previous plug-in matching behavior for virtual hosts,
set these attribute in the "Config" tag of the plugin-cfg.xml:
WebSphere Application Server component cumulative plug-in fix is NOT
available for WebSphere Application Server V4.0.1.
Testing recommendation
For WebSphere Application Server V4.0.2 through V4.0.4 configurations, it
is recommended that you test this component cumulative plug-in fix on your
test system before applying the fix to your production system. This should
identify any additional changes needed.
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 cumulative 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 this WebSphere Application Server V4.0 cumulative component
plug-in fix to WebSphere Portal Server V4.x configurations. WebSphere
Portal Server V4.x users must apply the WebSphere Application Server V5.0
component cumulative 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 and KeepAlive
timeout of http requests. This increase should be considered especially
when the Web server is remote and connection between the client and Web
server are slow (for example, when the client is using a modem connection
or the HTTP requests use POST):
Increased number of InterruptedException (Read timed out) exceptions
might 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)
ConnectionKeepAliveTimeout and 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.
Administrators should configure a thread-based Web server, such as IBM
HTTP Server V2.0, with WebSphere Application Server V4.0.2 through V4.0.7
on UNIX® for the best plug-in performance and overall performance. More
information about the benefits of running thread-based IBM HTTP Server
V2.0 Web server on UNIX platforms with WebSphere Application Server V4.0
is in technote:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21108347
Below is a list of file names and extensions needed for the V4.0 and V5.0
plug-ins, based on the Web server platform.
Platform and extension combinations for plug-in files
dll: Windows®
so: AIX®, Solaris™, Linux® (Intel® and OS/390®)
sl: HP-UX
All plug-in files for web servers that IBM supports
plugin_common: general plug-in file required to run any
supported Windows based web server or plug-in to a V4.0 application
server. It exists only for V4.0.
afpaplugin: AFPA support for IBM HTTP Server, needed for
support dynamic content caching if Dynacache in WebSphere is enabled. It
exists only for Windows based V4.0 and V5.0.
mod_was_ap20_server_http: plug-in module for IBM HTTP Server
2.0.42.x
mod_ibm_app_server_http: plug-in module for IBM HTTP Server
1.3.19.x and 1.3.26.x
mod_app_server_http: plug-in module for Apache 1.3.x Web
servers
mod_app_server_http_eapi: plug-in module for Apache 1.3.x with
Open SSL
ns_41_http: plug-in module for Windows based iPlanet 4.0 and
6.0
libns_41_http: plug-in module for all supported Unix based
iPlanet 4.0 and 6.0
domino5_http: plug-in module for Windows based Domino5 and
Domino6
libdomino5_http: plug-in module for all supported Unix based
Domino5 and Domino6 (except Solaris)
libdomino6_http: plug-in module for Solaris based Domino6
iisWASPlugin_http: plug-in module for the Windows based IIS4
and IIS5 Web server
IBM's cumulative plug-in fix is specific to the operating system. When
viewing the contents of that compressed file, you see only libraries
related to the appropriate operating system. For example, UNIX® libraries
are not packaged with the Windows cumulative plug-in fix, so you will not
see these when viewing this fix.
Prerequisites
None
Installation instructions
You must stop all Web server processes before you apply this plug-in
fix.
You can install this cumulative plug-in fix manually in a case that you
experience any problems to install it interactively or silently by using
the FixInstaller tool. Use the following as a guideline for manually
installing this component cumulative plug-in fix for WebSphere Application
Server V4.0:
Solution for manually installing cumulative plug-in fix
The following examples assume the use of the Java jar command. You can
also use other third-party decompression tools.
Steps for manually installing the V4.0 cumulative plug-in fix
Download the cumulative plug-in fix from the WebSphere
Application Server support site into a working temporary folder
outside the WebSphere install directory. The examples below use the
cumulative plug-in fix dated 16 September 2004, which is delivered in the
following format:
Verify that you set PATH to include the WebSphere JDK BIN folder and
run this command:
jar -xf WAS_Plugin_09-16-2004_4.0.X_cumulative_Fix_AIX.jar
Store all extracted libraries files within the BIN directory for the
folder where the extract takes place.
Stop all web services.
Back-up all current plug-in libraries.
Copy all new plug-in libraries from extracted BIN folder, overwriting
the previous ones. On AIX, run the slibclean command first, after
stopping the Web server to clean up any shared libraries in use.
Start all Web services again.
Verify that the plug-in build date has changed within the plug-in log
file.
Refer to the readme for detailed installation instructions.