[jboss-jira] [JBoss JIRA] (AS7-2266) Starting the server with a versioned backup fails the second time
Rajesh Rajasekaran (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Oct 26 10:43:45 EDT 2011
[ https://issues.jboss.org/browse/AS7-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637620#comment-12637620 ]
Rajesh Rajasekaran commented on AS7-2266:
-----------------------------------------
I think there would be several instances where the customer would want to restart using a configuration from several starts back, assuming one would always use the last configuration from 'current' is not valid.
There should be a way to tell the server to start from --server-config=2011xxxx-xxx2/v2
Right now the notion of --server-config=2011xxxx-xxx2 maps to snapshots.
I just have a feeling we have provided too many options here, and when we do that, we cannot afford to have any holes.
> Starting the server with a versioned backup fails the second time
> -----------------------------------------------------------------
>
> Key: AS7-2266
> URL: https://issues.jboss.org/browse/AS7-2266
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.0.Alpha1
> Reporter: Rajesh Rajasekaran
> Assignee: Brian Stansberry
> Labels: eap6-ux
>
> "--server-config=v? This will server the _xml_history/current folder for the configuration where ? is the number of the backup to use."
> "When restarting the server any existing standalone_xml_history/current directory is moved to a new timestamped folder within the standalone_xml_history, and a new current folder is created."
> Due to the above behavior starting the sever with --server-config=v1 works only the first time, but fails the second time with
> ERROR [stderr] java.lang.IllegalStateException: No configuration file ending in .v1.xml found in jbossas1/standalone/configuration/standalone_xml_history/current
> There is also no option currently to load the versioned copy from the new timestamped folder it is moved to.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list