Fix (APAR):  PK01733

Status:  Test

Release:  5.1.1.3,5.1.1.2,5.1.1.1,5.1.1,5.1.0.2,5.1.0.1,5.1.0,5.0.2.9,5.0.2.8,5.0.2.7,5.0.2.6,5.0.2.10

Operating System:  All

Supersedes Fixes:  PQ98391

CMVC Defect:  PK01733

Byte size of APAR:  9823

Date: 2005-04-14

Abstract:  Application files dropped on server restart

Description/symptom of problem:  Explicit schema initialization did not perform complete
initialization.  Portions of schema data were left uninitialized
until resource access.  Multiple threads are requesting resources
of the same type, causing the concurrent completion of the schema
initialization.  The initialization is not thread safe, leading to
a FeatureNotFoundException.

This problem was noted following the synchronization
(transferrance) of the configuration document 'deployment.xml'
from a DMgr note to all of the federated Application Server
nodes.

The problem has two symptoms, first, the loss of data following
the synchronization, for example, by causing application deployments to be dropped.  Second, the logging of an error by
FFDC, with the following text in the FFDC logs:

    Stack Dump = org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
    Feature 'name' not found.


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:  A dropped application may be restored by triggering a
a config synchronization from the dmgr manually.