APAR status
Closed as program error.
Error description
PQ92268 added selfchecking/selfhealing code when it though
corruption was found. We found that concurrent administrators
modify different fails (install ear, change a resource) causes
the code to slip and corrupt the serverindex.xml. This happens
because threads are not synchronized causing file access problem
therefore the code thinks files are missing/corrupted.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who have *
* DMGR at 5029. *
****************************************************************
* PROBLEM DESCRIPTION: When users are working on the *
* configuration concurrently, *
* serverindex.xml gets corrupted and the *
* following exception will be logged in *
* SystemOut.log randomly. *
* [1/25/05 20:52:31:113 EST] 520ae9 *
* ServerIndexMe E WKSP1001E: *
* Error loading resource *
* servers/RTWASdevi01caribou/server.xml *
* from context *
* cells/ECDEVINetwork/nodes/caribou -- *
* java.util.NoSuchElementException *
* at org.eclipse.emf.common.util. *
* BasicEList$EIterator.next *
* (BasicEList.java:1166) at *
* com.ibm.ws.sm.workspace.merger.impl. *
* ServerIndexMerger.getContentObject *
* (ServerIndexMerger.java:181) *
* at com.ibm.ws.sm.workspace.merger.impl. *
* ServerIndexMerger.selfCorrect *
* (ServerIndexMerger.java:123) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This problem is seen because 2 threads try to access the same
resource concurrently. Both the threads try to access the same
list. This list always contains only one element. Once one
thread gets the iterator it accesses the first element and
increments the iterator. The other thread then takes that
iterator and looks for the element which is not available,
resulting in the NoSuchElementException.
Problem conclusion
In order to solve this problem, the fucntion which accesses the
resource was synchronized.
This implies that every time a new iterator will be generated
for different threads.
This fix is scheduled for inclusion in 5.0.2.10 and 5.1.1.4.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg2700498
Temporary fix
*********
* HIPER *
*********
Comments
APAR information |
APAR number |
PK00346 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
YesHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-01 |
Closed date |
2005-02-04 |
Last modified date |
2005-05-06 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK04759
PK06246
Modules/Macros
Publications Referenced
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 |
|