[jboss-jira] [JBoss JIRA] (WFCORE-3712) Provided mechanism to disable configuration file backup

Brian Stansberry (JIRA) issues at jboss.org
Mon Mar 26 14:44:02 EDT 2018


    [ https://issues.jboss.org/browse/WFCORE-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551669#comment-13551669 ] 

Brian Stansberry commented on WFCORE-3712:
------------------------------------------

Analysis of this needs to account for all scenarios. For example, in the read-only-server-config=standalone.xml use case, it's the history that allows reload to work. Use case is that the config is golden but not modifiable, but if they use the CLI to affect some runtime behavior and have to reload to get that to work, the reload draws from history. IOW user is willing to temporarily shift a server off the golden image.

A possible behavior in that case is just to log something (INFO or WARN) in case of reload, and the server reloads back to the original config.

> Provided mechanism to disable configuration file backup
> -------------------------------------------------------
>
>                 Key: WFCORE-3712
>                 URL: https://issues.jboss.org/browse/WFCORE-3712
>             Project: WildFly Core
>          Issue Type: Enhancement
>            Reporter: Ken Wills
>
> For certain use cases, e.g. cloud with non-writable storage, the automatic persistence backup of configuration files (standalone.xml etc) is not needed or desired.
> It would be nice to have a mechanism to disable this.
> Example:
> {quote}
> 17:42:13,104 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/datagrid/standalone/configuration/standalone_xml_history/current to /opt/datagrid/standalone/configuration/standalone_xml_history/20180326-174213103
> 	at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:451) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1]
> 	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_161]
> 17:42:13,106 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {quote}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list