Ah ha! I found the root cause: ServiceController.start() : 340
And a similar "problem" in: ServiceController.stop() : 426 So the question still stands: is it desired that a failed service cannot be restarted? And if so, why? I can certainly see where, on initial startup, that you don't want a failed service to continually be re-start()'d while the dependecies are unwound. But after this, shouldn't a restart be allowed? This would allow a defective service to be repaired and restarted. Given ServiceController.start() (minus the offending check for FAILED), a restarted service will then finish starting any dependent services. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845230#3845230 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845230 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
