PH51481: ERRORS READING CONFIGURATION FILES CONTAIN INSUFFICIENT DETAIL

APAR status

• Closed as program error.

Error description

• In the case a xml file is bad and has a problem reading the
  file, the error message doesn't indicate while xml file had the
  problem.
  
  For example, when a variables.xml file was zero bytes and the
  server failed to start, but you can't determine which file was
  bad with this error message:
  
  java.lang.IllegalStateException:
  com.ibm.ws.exception.WsRuntimeException:
  com.ibm.ws.exception.ConfigurationError:
  org.xml.sax.SAXParseException: Premature end of file.
  	at com.ibm.ws.runtime.component.VariableMapImpl.reload(Variabl
  eMapImpl.java:240)
  	at com.ibm.ws.runtime.component.VariableMapImpl.initialize(Var
  iableMapImpl.java:150)
  	at com.ibm.ws.runtime.WsServerImpl.bootVariableMap(WsServerImp
  l.java:497)
  	at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:202)
  
  	at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:720)
  	at com.ibm.ws.runtime.WsServer.main(WsServer.java:59
  ...
  Caused by: com.ibm.ws.exception.WsRuntimeException:
  com.ibm.ws.exception.ConfigurationError:
  org.xml.sax.SAXParseException: Premature end of file.
  	at com.ibm.ws.runtime.config.DocumentLocatorImpl.getDocumentOb
  jects(DocumentLocatorImpl.java:65)
  	at com.ibm.ws.runtime.component.VariableMapImpl.reload(Variabl
  eMapImpl.java:194)
  	... 31 more
  Caused by: com.ibm.ws.exception.ConfigurationError:
  org.xml.sax.SAXParseException: Premature end of file.
  	at com.ibm.ws.runtime.config.ConfigDocumentImpl.load(ConfigDoc
  umentImpl.java:232)
  	at com.ibm.ws.runtime.config.ConfigServiceImpl.getDocument(Con
  figServiceImpl.java:182)
  	at com.ibm.ws.runtime.config.ConfigServiceImpl.getDocumentObje
  cts(ConfigServiceImpl.java:126)
  	at com.ibm.ws.runtime.config.DocumentLocatorImpl.getDocumentOb
  jects(DocumentLocatorImpl.java:51)
  	... 32 more
  Caused by: org.xml.sax.SAXParseException: Premature end of file.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  8.5 and 9.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Errors processing configuration files   *
  *                      do                                      *
  *                      not specify which file was being        *
  *                      processed                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an exception (such as a failure in XML parsing) occurs
  while processing a server configuration file, a WAS
  ConfigurationError is thrown, wrapping the original exception.
  This error, however, does not include any information regarding
  what file was being processed when the failure occurred (and, as
  in the example in the APAR description, it is not often included
  in the original exception). This often required users to gather
  detailed tracing and engage IBM support in order to determine
  the file at issue, rather than being pointed to it immediately
  and being able to fix it on their own.
  

Problem conclusion

• Message text was added to the ConfigurationError containing the
  path of the file being processed.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.24 and 9.0.5.16. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• 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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels