Fix (APAR): WAS_Plugin_09-16-2004_4.0.X_cumulative_Fix Status: Fix Release: 4.0.7,4.0.6,4.0.5,4.0.4,4.0.3,4.0.2,4.0.1,4.0.0 Operating System: All Supersedes Fixes: WAS_Plugin_04-02-2003_4.0.X_cumulative_Fix WAS_Plugin_12-09-2003_4.0.X_cumulative_Fix WAS_Plugin_10-01-2003_4.0.X_cumulative_Fix WAS_Plugin_07-23-2003_4.0.X_cumulative_Fix 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 - .0.2.1 plugin introduces a performance problem for all subsequ CMVC Defect: WAS_Plugin_09-16-2004_4.0.X_cumulative_Fix Byte size of APAR: 8007156 Date: 2004-09-16 Abstract: WebSphere Plug-in Cumulative 4.0.X fix 09-16-2004 Description/symptom of problem: WebSphere Plug-in Cumulative 4.0.X fix 09-16-2004 Directions to apply fix: 1) Create temporary "fix" directory to store the jar file: Unix: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Stop Web server **AIX ONLY: run the command slibclean after stopping the Web server to clean up any shared libraries in use 4)Create a /Fix directory if one does not already exist 5) Run the jar file with the following command answering questions/prompts as they appear: java -jar -backupJar /Fix/_backup.jar NOTE: In a remote webserver environment where the full app server is not installed you will need to run the command with additional command line options in order for the install to work successfully: java -jar -skipContainerCheck -dupCheck no -updateXML no 6) Restart Web Server 7) The temp directory may be removed but the jar file should be saved. Do not remove any files created and stored in the /Fix directory. These files are required if a fix is to be removed. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Change directory to the fix location (/Fix). 2) Stop Web server 3) Run the backup jar file with the following command: java -jar 4) Restart Web server Directions to re-apply fix: Follow the instructions for applying a fix. If the backup files still exist (from the previous fix application), you will be prompted to overwrite. Answer "yes" at the overwrite prompts. Additional Information: Name PQ88879 Abstract Plug-in returned success code while failed to load new plugin-cfg.xml Plug-in did not set the error code and returned the successful code when it failed to load the updated plugin-cfg.xml. For IIS plug-in, this could cause the Web server to hang. Name PQ89583 Abstract Plug-in marked the appserver down incorrectly The WebSphere plug-in improperly marks the application server down and retried the POST request on a different Application Server. For POST request, after POST data being read from the input stream, it cannot be retried. Plug-in should fail the request when the request cannot go through. Name PQ92641 Abstract Apache plug-in did not send the client SSL certificate WebSphere Apache plug-in did not send the client SSL certificate to application server via application server internal header. The correct Apache Web server environment variable SSL_CLIENT_CERT is now being used to retrieve the client SSL certificate. Plug-in also strips out the footer, header, and newline characters from the certificate so that the certificate is in the format that the application server expects. Name PQ93112 Abstract Unclosed Connections caused plug-in performance degradation When plug-in received Windows-style "Connection: Close" header, it did not process the header correctly, and did not close the connection. This would introduce a performance degradation.