I remember we talked about it. Although I don't remember why we didn't do it. It
could just be that it didn't make the schedule.
On Aug 27, 2012, at 11:19 AM, John Mazzitelli <mazz(a)redhat.com> wrote:
I have a question on the reload-required and restart-required
states.
I see in the root resource, if you know you need to reload to pick up config changes, you
can invoke the reload op ("/:reload)").
In the case of restart required, obviously the JVM needs to be restarted.
Has anyone given any thought of providing some sort of restart operation on the root
resource, like "/:restart", in which the AS7 will actually exit the VM with a
specific exit code (say, something odd like 155 or whatever - e.g. System.exit(155)) which
can then be interpreted by the parent process (standalone.sh) to say "oh, the JVM
exited, but the server wants me to restart it immediately". So standalone.sh script
could then turn around and immediately restart the vm again.
This would help things such as customized installers that want to re-configure AS7 to run
with a particular set of config settings that are needed for a particular app to run but
will not require the user to perform manual restarting of the VM after the installer does
its thing (as is the case for what I'm doing with RHQ/JON).
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev