- This topic has 5 replies, 3 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
I just recently noticed that when stopping an application server in MyEclipse, it is no longer handled gracefully. It seems the JVM is just abruptly terminated. This is a huge benefit most of the time since it makes restarting much quicker. However, it is a major pain if you’re trying to test something that requires a clean termination of the server. One such case is session persistence. If you are using a server that persists HTTP sessions to the file system on shutdown, it saves you having to restart your session when you restart your server. This is really useful for testing complex webapps (especially those with logins). Unfortunately, when the JVM is forced to quit, the shutdown hooks that normally handle the persisting of the session are not fired.
It would be nice to have that feature back, maybe as an option?
IronDuck,
I think you just outlined a good argument for making a forced quite an option. I’ll file this as an enhancement, in the mean time are you able to get around this by starting/stopping your app server externally (and using remote debugging if necessary) while testing the sessions persistence? This won’t likely make it into 5.0, because our TODO list is full.That’s cool. It’s a minor invonvenience right now, but I assume it would be possible to reimplement since the functionality used to exist. As long as it’s on someone’s radar, I’m happy. Keep up the great work!
Definately, I filed it as an option to add under the server configuration, essentially “Force application exit” or something to that extent. We had another user provide some very good reasons why killing the app server in an enterprise app can really be a problem, so I hope this can go into 5.0.1 or so, I don’t think it will make the 5.0 cut, and there is also the issue of the *new* connectors that we may adopt from WTP, so lots of stuff to evaluate.
@support-rkalla wrote:
IronDuck,
I think you just outlined a good argument for making a forced quite an option. I’ll file this as an enhancement, in the mean time are you able to get around this by starting/stopping your app server externally (and using remote debugging if necessary) while testing the sessions persistence? This won’t likely make it into 5.0, because our TODO list is full.Please note. You need only STOP the server externally.
You can actually START the server internally with normal debugging.
Furthermore I have assigned an external script (a simple jboss shutdown -S) to Eclipse’s ‘run as’ button, so now the graceful shutdown is accomplished internally as well.Hope this helps.
-nat
