Fix (APAR):  PQ67535

Status:  Fix

Release:  4.0.5

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PQ67535

Byte size of APAR:  1063171

Date: 2003-05-14

Abstract:  Retry Naming Operation Needed  for StaleConnectionException

Description/symptom of problem:  When the database server used for the admin repository is stopped and restared, name server operations against the database will initially fail, when in principle, the name server could retry the naming operation.  This would a void the need for naming clients to perform the retry.

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:  Two new WebSphere naming properties were defined:

. com.ibm.websphere.naming.db.retrycount: to control the number of retries and the default value of this property is 2.

. com.ibm.websphere.naming.db.retrydelay: to control the delay between retries. The default value of this property is 2000 milliseconds.

To use non-default values for those two properties, add the following two lines into the file %WAS_INSTALL_DIR%\AppServer\admin.config:

com.ibm.websphere.naming.db.retrycount= your_value
com.ibm.websphere.naming.db.retrydelay= your_value

NOTE: stop adminServer before you edit the file admin.config. After finishing the insertion, new values of the properties should be in effect after restarting adminServer.