APAR status
Closed as program error.
Error description
The dmgr process is recycled and the nodeagents start remove
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Uses of WebSphere Application Server *
* releases 5.0.2.x and 5.1.x. *
****************************************************************
* PROBLEM DESCRIPTION: The WCCM initialization code is not *
* thread safe during initialization. In *
* particular, this can cause an exception *
* to be thrown during the synchronization *
* of the configuration, causing the *
* apparent removal of application data *
* from the deployment manager *
* configuration. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem occurs randomly during synchronization, for
example when performing a full synchronization from the
administrative console.
The steps to perform full synchronization are:
Open the admin console and log in;
Expand the "System Administration" section;
Select "Nodes";
A new screen lists the configured nodes;
Check an application server node;
Push the "Full Resynchronization" button;
Wait for synchronization to complete.
Following synchronization, data is missing from the
configuration in the deployment manager installation, from
the directory:
<WAS_HOME>/config/cells/<cellname>/applications
A consequence of the missing application data is for the
NodeAgent to throw a NullPointerException (NPE).
The FFDC logs for the deployment manager may show the
following error:
org.eclipse.emf.ecore.resource.Resource$IOWrappedException
com.ibm.ws.management.sync.FolderCompareTask.
updateNodeAppList
Exception = org.eclipse.emf.ecore.resource.Resource$
IOWrappedException
Source = com.ibm.ws.management.sync.FolderCompareTask.
updateNodeAppList
probeid = 259
Stack Dump = java.lang.NullPointerException at
org.eclipse.emf.ecore.impl.EClassImpl.getEStructuralFeature
(EClassImpl.java:461)
...
The deployment manager system output log ("SystemOut.log") may
show the following error:
4/29/04 15:54:58:095 CDT 42bb13 TraceNLS u
No message text associated with key
Encountered.an.exception.while.building.the.list.of.
applications:.{0}
in bundle com.ibm.ejs.resources.seriousMessages
4/29/04 15:54:58:087 CDT 42bb13 ApplicationDe E
Encountered an exception while building the list of
applications:
org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
Feature 'name' not found. (deployment.xml, 10, 122)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue
(XMLHandler.java:1032)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.
handleObjectAttribs
(SAXXMIHandler.java:146)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.
createObjectFromFactory
(XMLHandler.java:828)
Problem conclusion
Fix created and published. This fix is included in the 5.0.2.7
fixpack.
Temporary fix Comments
APAR information |
APAR number |
PQ89391 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-05-26 |
Closed date |
2004-09-13 |
Last modified date |
2004-09-13 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
|