APAR status
Closed as program error.
Error description
Applications are removed after deployment manager recycle
randomly. Performing a full resynchronization of the node
will readd 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.createObjectFromFactor
y(XMLHandler.java(Compiled Code))
...
Local fix
Performing a manual full resynchronization of the node
did readd 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
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.
Problem conclusion
Fix was created and published; fix is incorperated into
5.1.1.5 and 5.0.2.11.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Note that the fix is installable on 5.1.1.4.
Temporary fix Comments
APAR information |
APAR number |
PK01733 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-25 |
Closed date |
2005-05-12 |
Last modified date |
2007-12-30 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK58716
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|