Fix (APAR):  PQ70205

Status:  Fix

Release:  4.0.5,4.0.4,4.0.3,4.0.2

Operating System:  All

Supersedes Fixes:  



CMVC Defect:  PQ70205

Byte size of APAR:  912587

Date: 2003-02-12

Abstract:  WEBSPHERE FAILS TO HANDLE POST REQUESTS WHEN THE POST DATA IS SENT IN TIME INTERVALS GREATER THAN THE CONNECTION TIMEOUT

Description/symptom of problem:  WebSphere fails to handle post requests when the post data is sent in time intervals greater than the connection timeout.  WebSphere needs to handle this situation and return the correct status code.The plugin also needs to be modified slightly to limit the possibility of sending this type of request to the application server.  The plugin
change was done as part of PQ70037.



Directions to apply fix:  
1) Create temporary "efix" directory to store the jar file:
 				AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
 		  Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.  Do not remove
	any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<efix> directories.
   These files are required if an efix is to be removed.




Directions to remove fix:  
NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
 		ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
			 removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<efix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
	java -jar <backup_efix#>

4) Restart WebSphere




Directions to re-apply fix:  
Follow the instructions for applying an efix.

If the backup files still exist (from the previous efix application), you will be prompted to overwrite.

Answer "yes" at the overwrite prompts.



Additional Information:  This eFix includes PQ70202
=============================
WEBSPHERE THROWS 500 ERRORS WHEN ATTEMPTING TO HANDLE REQUESTS

WebSphere throws 500 errors when attempting to handle requests WebSphere's plugin marks the application server as down and fails to handle any future requests to the application server until the applications server is recycled. When looking at trace, only  one transport thread is being allocated to receive requests and  the request is never passed to the webcontainer.