[jbossts-issues] [JBoss JIRA] (JBTM-1586) reloadDomain reloadServer: reload configuration server operation (compatable with svn update)
Tom Jenkinson (JIRA)
jira-events at lists.jboss.org
Mon Mar 25 12:02:42 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson moved BLACKTIE-228 to JBTM-1586:
----------------------------------------------
Project: JBoss Transaction Manager (was: Blacktie)
Key: JBTM-1586 (was: BLACKTIE-228)
Component/s: BlackTie
(was: Admininstration)
> reloadDomain reloadServer: reload configuration server operation (compatable with svn update)
> ---------------------------------------------------------------------------------------------
>
> Key: JBTM-1586
> URL: https://issues.jboss.org/browse/JBTM-1586
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Tom Jenkinson
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> reloadDomain: This method is available from the "control" tab of a domain and operates on all servers
> reloadServer:
> it would be useful to have a reload server configuration operation.
> this will require an external shell script to repeatedly start server.exe processes dependent upon exit status of server.exe
> the serverdone operation can then be altered to return a specific return code dependent upon whether shutdown/reload configuration was issued.
> The use of this method is if the environment.xml file has changed the server can be rebooted with the new configuration file
> the shell script would look like (we would need one for windows and one for linux):
> int startServer = 1;
> while (startServer)
> int exitStatus = server.exe();
> if (exitStatus == reloadConfiguration) {
> startServer = 1;
> svn update configuration;
> } else {
> startServer = 0;
> }
> NOTE: This method does not take an id parameter as all servers must be reloaded
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list