Company policy requires read-only config, JBoss will not start
Issue
- Per company policy, JBoss configuration must not be changed on a running server. File permissions are set to read-only in support of this policy which causes startup to fail with the exception below. I could not find instructions to disable the configuration-history component and setting current-history-length and history-days to 0 had no effect on startup. How can JBoss be configured to start with a read-only configuration?
17:12:00,745 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: java.lang.IllegalStateException: JBAS014642: Could not create $JBOSS_HOME/standalone/configuration/standalone_xml_history
at org.jboss.as.controller.persistence.ConfigurationFile.mkdir(ConfigurationFile.java:568) [jboss-as-controller-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:449) [jboss-as-controller-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:306) [jboss-as-controller-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
....
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
