Fixes are available
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Exception seen on JVM Startup from corruption of Namestore.xml occuring due to possible Race condition is: [9/22/11 11:50:11:095 CEST] 00000000 WsServerImpl E WSVR0009E: Error occurred during startup... Caused by: com.ibm.ws.naming.distcos.NameSpaceConstructionException: Unexpected error reading name store document. at com.ibm.ws.naming.distcos.PersistentNameStoreManager.readInRootC txFromXm l(PersistentNameStoreManager.java:397) ... Caused by: com.ibm.ws.exception.ConfigurationError: org.xml.sax.SAXParseException: Premature end of file. at com.ibm.ws.runtime.config.ConfigDocumentImpl.load(ConfigDocument Impl.jav a:193) ... Caused by: org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti on(Unknown Source) Nameserver shutdown should force a Wait until Write operation has completeed.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: The persistent name bindings file, * * namestore.xml, becomes corrupted in * * the master repository. * **************************************************************** * RECOMMENDATION: * **************************************************************** The persistent name bindings file, namestore.xml, becomes corrupted in the master repository. It is not clear how this condition occurs unless the deployment manager or standalone server is stopped with an operating system command, for example, with "kill -9", instead of through the stopManager or stopServer shell script. Frequent persistent binding updates make the condition more likely to occur, although the Information Center states that the persistent binding implementation is not designed for frequent binding updates.
Problem conclusion
The new custom property, naming.persistent.ignoreReadError, can be set to "true" so that read errors on namestore.xml are ignored when it is read during process startup. This causes the corrupted file to be replaced if a persistent binding update request is later received. The binding data in the corrupted file is then lost. If all persistent binding data is regenerated automatically, as is often the case, the lost binding data should not cause a problem. If loss of binding data is a problem, this property should not be used. The property can be set as a cell, node, or name server custom property. If set as a cell custom property, all server processes in the cell will respond to the setting. Likewise, if set as a node custom property, all server processes in the node will respond to the setting. Settings at narrower scopes override settings at wider scopes. For example, a setting at the name server scope will override settings at the node or cell scope. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.23 and 8.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM53514
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-05
Closed date
2012-03-12
Last modified date
2012-03-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021