PQ67088: LAUNCH CLIENT DOES NOT CLEAN UP TEMPORARY DIRECTORY WHERE EAR EXPANDED.

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
Under certain circumstances where a machine is very busy the
backround process that is started by the lauch client to clean
up the temporary ear directory may not be cleaned up.
.
This APAR adjusts the interval of time the process waits prior
to attempting to delete the files.
Local fix
No workaround exists
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server or WebSphere    *
*                 Application Server Client users running      *
*                 launchClient command.                        *
****************************************************************
* PROBLEM DESCRIPTION: When running a J2EE Application Client  *
*                      using the launchClient command, the     *
*                      temporary directory created by the      *
*                      WebSphere Application Client runtime    *
*                      does not always get deleted on some     *
*                      systems. These temporary directories    *
*                      are created in the user's temporary     *
*                      file location and have the form:        *
*                      WSTMPCCnnnnnn, where nnnnnn is a        *
*                      random number.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Client runtime creates a temporary
directory which it uses to expand the Enterprise Archive file.
This temporary directory is used to run the client application
and while it's running these files are locked by Java.  When
the client application terminates, the WebSphere Application
Client runtime attempts to delete the temporary directory. If
the directory cannot be deleted, it waits 250ms, and then tries
again, up to 10 times.  In most cases, the files are unlocked
and can be deleted within the first couple of tries.  However,
on some systems, 10 retries is not enough.
Problem conclusion
The default retry count was changed from 10 to 1000.
Also a new parameter can be specified on the launchClient
command.  The new parameter is:
-CCdeleteFileRetryCount=<number of retries>.  For example:
-CCdeleteFileRetryCount=300

Note:  The WebSphere Application Client runtime will only retry
until the files are deleted or the retry count has been reached.
Temporary fix Comments
APAR information
APAR number PQ67088
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-10-10
Closed date 2002-12-16
Last modified date 2002-12-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
CLIENT          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67088
IBM Group: Software Group
Modified date: Dec 16, 2002