You could always go outside of JBoss to do this - you can on your own determine the process PID that your run.sh started and issue a kill yourself. This might mean tweeking run.sh or any wrapper startup script that you use so you get the PID (perhaps have the script dump out to stdout the PID number?). This would allow you to not have to rely on any feature deployed or not deployed in JBoss - its also more kludgy than using the JBoss shutdown mechanism :-) It also means you can only kill JBoss instances on the local box where you issue the kill.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861962#3861962 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861962 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
