Fix (APAR):  PQ76492

Status:  Fix

Release:  5.0.2

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PQ76492

Byte size of APAR:  15986

Date: 2003-07-28

Abstract:  MaxSendSize and MaxReceiveSize fix.  NoActvityException fix

Description/symptom of problem:  In PME 502 Work Area service the values for MaxSendSize and
MaxReceiveSize got hard coded to their default values rather than the user specified values.  A user can specify the values for MaxSendSize and MaxReceiveSize under the Work Area Service in the Admin Console.  These values are the correct values with which the Work Area Service should use.  However, in 502, these vaules are hard coded to a default value and the values set by a user are disregarded. This fix will change the code such that the user specified values are actually used.  This fix will also address another very minute issue, but one that needs addressed.  In 502, when a user calls one of the API methods (e.g get/set/getName/etc) on Work Area prior to doing a begin (a perfectly legal
action), a NoActivityException is thrown.  This exception is caught and handled by Work Area and the appropriate action is taken.  So from the users point of view they still see the same result as in previous releases.  However, the NoActivityException is logged to the FFDC files and if debug is turned on the exception is printed to the debug logs.  There could potentially be many of these exceptions which could lead to concerns or false blame by a user.  It also leads to a performance degradation, albeit small, due to the fact that an exception is thrown (potentially many times).  We have found a better way to provide our functionality that won't cuase this exception to be thrown.

Directions to apply fix:  NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

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) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may 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) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Additional Information: