PK59387: EJBDEPLOY LEAVES BEHIND TEMP DIRECTORIES WITHIN THE DEPLOYED APPLICATION DIRECTORY.

Rational Software Architect, Version 7.0.0.7
Rational Application Developer for WebSphere Software, Version 7.0.0.7
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.1.7: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 7
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When running EJBDeploy, the temp working directory created does
  not get cleaned out in AST/RAD 6.0 onwards.
  
  This has been identfied as a BUG and might be related to the
  following method ie AddShutdownhook
  
   http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Runtime.html#
  addShutdownHook(java.lang.Thread)
  

Local fix

• Clean the directory manually. But in a multiproject/multi member
  teams this can cause confusion and needs to be addressed within
  the EJBDeploy call.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the command-line EJB Deploy     *
  *                 code generation tool in IBM WebSphere        *
  *                 Application Server V6.0 and V6.1             *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the -keep command-line flag is not   *
  *                      specified then the EJB Deployment       *
  *                      working directory is not deleted.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the -keep command-line flag is specified for EJBDeploy then
  it will not delete the working directory upon completion of
  the code generation.  However, if -keep is not specified then
  it is suppose to delete the working directory but this does
  not occur as certain files are still locked by the JVM when
  the deletion occurs, preventing the working directory from
  being completely cleaned.
  

Problem conclusion

• If -keep is not specified then the ejbdeploy scripts
  (ejbdeploy.bat on Windows and ejbdeploy.sh on UNIX platforms)
  will now be responsible for deleting the working directory
  after the ejbdeploy JVM is terminated.  The fix for this APAR
  is currently scheduled for inclusion in the WebSphere
  Application Server v6.0.2.29 and v6.1.0.19 fix packs.  Please
  refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R600 PSY

     UP

• R610 PSY

     UP