DevTest IAM fails on Restart

Products

• Service Virtualization

Issue/Introduction

IAM fails to restart and gets this error:

2025-08-11 10:59:03,817 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
    at org.jboss.as.server.ServerService.boot(ServerService.java:403)
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
    at java.lang.Thread.run(Thread.java:748)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character (NULL, unicode 0) encountered: not valid in any content
 at [row,col {unknown-source}]: [1,1]
    at com.ctc.wstx.sr.StreamScanner.constructNullCharException(StreamScanner.java:659)
    at com.ctc.wstx.sr.StreamScanner.throwInvalidSpace(StreamScanner.java:683)
    at com.ctc.wstx.sr.StreamScanner.throwInvalidSpace(StreamScanner.java:674)
    at com.ctc.wstx.sr.StreamScanner.getNextAfterWS(StreamScanner.java:844)
    at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2119)
    at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180)
    at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203)
    at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:74)
    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
    ... 3 more

2025-08-11 10:59:03,817 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
2025-08-11 10:59:03,817 INFO  [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: Keycloak 15.0.0 (WildFly Core 15.0.1.Final) stopped in 4ms

Environment

DevTest 10.7.2 GA

Cause

The issue was caused due to a corrupted {{IAM_HOME}}\standalone\configuration\standalone.xml file.

Resolution

Deleted the current standalone.xml and restored from a backed up file in of the {{IAM_HOME}}\standalone\configuration\standalone_xml_history folders.

Copied a standalone.v1.xml file to the {{IAM_HOME}}\standalone\configuration folder and renamed to standalone.xml.

Able to bring up IAM and all the other components.

Machine scanners can sometimes corrupt this file.

Additional Information

A corrupted standalone.xml file, often associated with JBoss/WildFly application servers, can lead to service failures or unpredictable behavior. This file defines the server's configuration, including network settings, deployments, and logging.

Implement Regular Backups:
Regularly back up the standalone.xml file and the entire configuration directory.