I think there are two separate issues:
1) Restarting GF in the event GF itself crashes - this needs something
external, I think any SO provides a mechanism
2) Trigger a restart in GF when settings are changed - what about GF
creating a process at shutdown time, and having this process to launch
another GF instance when the first one is gone, and then killing
itself (I am not sure this can be done inside the same JVM)
- or even better -
What about avoiding GF having to be restarted when some of the settings
change? Do we really need to restart GF to change the port it is
listening to for example or to change the classpath?
I know that implementing things like that is not trivial, they add
complexity without any real benefit, but I think they should be taken
into account (maybe the next version?)
Piero
glassfish_at_javadesktop.org wrote:
> Will,
>
> This has been a long-standing request and though this is a rather intricate issue of restarting a
> process from within itself.
>
> The approach of "Platform Specific Service Mechanism" like SMF/Windows-Services may not help us here, because this is actually a legitimate shutdown followed by a start operation. There is
> a possibility of exiting with a specific exit code and then rely on operating system to bring the
> process back up.
>
> Another problem is that users don't always like creating an operating system service for GlassFish server process.
>
> A watchdog can be thought of as an option, but that increases the number of processes to 2 and
> that too is not well accepted by most.
>
> This needs some careful thought ...
>
> - Kedar
> [Message sent by forum member 'km' (km)]
>
> http://forums.java.net/jive/thread.jspa?messageID=236638
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>