PK01733: 5.0.1: Problems with removal of config files during startup
 Downloadable files
 
Abstract
PQ89391 does not correct all problems with removal of config files during startup.
 
Download Description
PK01733 resolves the following problem:

ERROR DESCRIPTION:
Applications are removed after deployment manager recycle randomly. Performing a full resynchronization of the node will read these applications to the nodes successfully.This was not addressed in the previous fix PQ89391.
The following is seen in the dmgr FFDC logs:
Stack Dump = org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
Feature ´name´ not found.
(cells/<cell_name>/applications/<app_name>/deployments/<app_name>/ deployment.xml, ##, ###)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHand ler.java(Compiled Code))
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAttribs(SAXXMIHandler.java(Compiled Code))
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory(XMLHandler.java(Compiled Code))

LOCAL FIX:
Performing a manual full resynchronization of the node did read the applications to the node in this client´s scenario.

PROBLEM SUMMARY:

USERS AFFECTED:
WebSphere Application Server users with a federated topology.

PROBLEM DESCRIPTION:
Problems with synchronous access to incompletely initialized schema meta-data can cause applications to be dropped on a Dmgr restart.

RECOMMENDATION:
Explicit schema initialization did not perform complete initialization. Portions of schema data were left
un-initialized 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 (transference) 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.

PROBLEM CONCLUSION:
Fix was created and published; fix is incorporated into 5.1.1.6 and 5.0.2.11.

Note: The fix package 'PK01733.jar' is installable up to 5.1.1.4.

The fix package 'PK01733_5115.jar' updates the prerequisite settings to allow the fix to be installed on 5.1.1.5.

If you are installing the fix on 5.1.1.5, you must use the 'PK01733_5115.jar' package.

Please refer to the recommended updates page for delivery information:
General/swg27004980.html
 
Prerequisites
Please download the UpdateInstaller below to install this fix.
 
URL LANGUAGE SIZE(Bytes)
UpdateInstaller US English 7250000
 
 
Installation Instructions
Please review the readme.txt for detailed installation instructions.
 
URL LANGUAGE SIZE(Bytes)
Readme US English 2791
 
Download package
What is DD?
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
PK01733.jar 5/12/2005 US English 9823 FTP DD
PK01733_5115.jar 7/6/2005 US English 9859 FTP DD
 
Technical support
1-800-IBM-SERV (U.S. Only)
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server for z/OS Not Applicable
Application Servers Runtimes for Java Technology Java SDK
Problems (APARS) fixed
PK01733, PQ98391
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): z/OS
Software version: 5.1.1.5
Software edition:
Reference #: 4009628
IBM Group: Software Group
Modified date: Jul 8, 2005