PQ91999: THE TEMPORARY JSP FILES FOR A ENTERPRISE APPLICATION ARE NOT CLEANED UP WHEN UNINSTALLING AN ENTERPRISE APPLICATION.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When uninstalling an enterprise application the temporary JSP
files located in <WAS_HOME>/temp directory are still left there.
If the client installs a new ear file where the JSP will need
to be compiled, but the jsp file was not directly updated, this
fails.  This fix will clean up the temporary JSP files when the
ear file uninstalled.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: When uninstalling an enterprise         *
*                      application the temporary JSP files     *
*                      located in <WAS_HOME>/temp directory    *
*                      are not deleted.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the client installs a new ear file in which the JSPs need
to be compiled, but the jsp file was not directly updated, the
install fails.
Problem conclusion
This fix will clean up the temporary JSP files when the ear
file is uninstalled.

Two articles in the WebSphere Application Server InfoCenter have
been updated to include the information for this APAR. To access
the latest online documentation, go to:


http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp

The change includes information added to the "Example: Setting
JVM Custom Properties" article (xrun_jvm.html), as follows:

com.ibm.websphere.deletejspclasses

Deletes JSP classes for all applications after those
applications have been deleted or updated. By default, the
value of this property is true.

Steps for this task

1. Connect to the administrative console and navigate to the
   Java Virtual Machine Custom Properties panel.

   Base configuration:  Servers > Application Servers >server1
   > Process Definition > Servant > Java Virtual Machine >
   Custom Properties

   ND configuration:  System Administration > Node Agents >
   nodeagent > Process definition > Control > Java Virtual
   Machine > Custom Properties

2. If the com.ibm.websphere.deletejspclasses property is not
   present in the list, create a new property name.

3. Enter the name and value.

com.ibm.websphere.deletejspclasses.delete

Deletes JSP classes for all applications after those
applications have been deleted, but not after they have been
updated. By default, the value of this property is true.

Steps for this task

1. Connect to the administrative console and navigate to the
   Java Virtual Machine Custom Properties panel.

   Base configuration:  Servers > Application Servers >server1 >
   Process Definition > Servant > Java Virtual Machine > Custom
   Properties

   ND configuration: System Administration > Node Agents >
   nodeagent > Process definition > Control > Java Virtual
   Machine > Custom Properties

2. If the com.ibm.websphere.deletejspclasses.delete property is
   not present in the list, create a new property name.

3. Enter the name and value.


com.ibm.websphere.deletejspclasses.update

Deletes JSP classes for all applications after those
applications have been updated, but not after they have been
deleted. By default, the value of this property is true.

Steps for this task

1. Connect to the administrative console and navigate to the
   Java Virtual Machine Custom Properties panel.

   Base configuration:  Servers > Application Servers >server1
   > Process Definition > Servant > Java Virtual Machine >
   Custom Properties

   ND configuration:  System Administration > Node Agents >
   nodeagent > Process definition > Control > Java Virtual
   Machine > Custom Properties

2. If the com.ibm.websphere.deletejspclasses.update property is
   not present in the list, create a new property name.

3. Enter the name and value.

 -------------------------------------------
The change also consists of a note added to the "Developing
JavaServer Pages files with WebSphere extensions" article,
(tweb_aov3jsp.html) as follows:

NOTE: You can choose to have the compiled JSP files in
the WAS_HOME/temp directory deleted when the associated
application is updated or deleted. You do this by setting
the com.ibm.websphere.deletejspclasses,
com.ibm.websphere.deletejspclasses.delete, or
com.ibm.websphere.deletejspclasses.update system property for
the node agent of the node on which the application will be
updated or deleted. For more information about setting these
properties, see "Example: Setting Custom JVM Properties".

APAR PQ91999 is associated with SERVICE LEVEL W502016 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ91999
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-07-26
Closed date 2004-10-07
Last modified date 2004-11-01

APAR is sysrouted FROM one or more of the following:
PQ87615

APAR is sysrouted TO one or more of the following:
PQ92101

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ93769    UP04/10/15 P F410

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ91999.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ91999
IBM Group: Software Group
Modified date: Nov 1, 2004