The trick, however, is to continue to notify the service controller of your status -- which the java wrapper stuff exposes a java method to give him hints on start / stop status. This is important in windows services to get the appopriate status and to make sure the Windows Service Manager doesn't think you're ignoring him.
Jeff
Ivelin Ivanov wrote:
Would it use native code to restart the JBoss services
or would it just ask the deployers to undeploy and redeploy all services?
Ivelin
--- Jeff Haynie <[EMAIL PROTECTED]> wrote:
We use
http://wrapper.tanukisoftware.org/doc/english/ with
JBoss on both Windows and Linux and it handles all of this
out-of-the-box (restart failure, retry logic, etc.)
I would recommend it instead of rolling your own. They've even got a MBean for managing restarts, etc.
I'll be glad to contribute / patch our jboss
startup/shutdown wrapper around ServerImpl that controls the service manager
lifecycle if it would help.
Jeff
Ivelin Ivanov wrote:
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
