[mod_cluster-dev] mod-cluster and kill -9

Hi Paul, wanted to reiterate the importance of [1] for the next release of mod-cluster. I'm constantly running into this when I deploy httpd/mod-cluster and JBoss 5.1.0 on Amazon's EC2 cloud. The easy way to stop an instance (OS + JBoss) on EC2 is to 'terminate' it via the AWS Console, which shuts down the OS ("shutdown -h now"). Unfortunately, our AMIs only had an S98jboss in /etc/rc4.d for starting JBoss, but no corresponding K98jboss for stopping it *gracefully* on shutdown. Therefore the process was always killed via -9. This caused very long timeouts and 5XX HTTP responses, until httd/mod-cluster finally figured out that the worker crashed and failed over to a different worker. As a workaround, I created a K98jboss link so now JBoss is shut down gracefully when the host is terminated. However, I figure we can get into this situation in many different ways, e.g. * Not providing a K98jboss script on EC2 * Killing JBoss with -9 via a script (I've seen this many more than once * Pulling a blade out of the rack. A crude way of shutting down an instance, but that's normal in large clusters ! Can we have this feature in mod-cluster 1.1 ? [1] https://jira.jboss.org/jira/browse/MODCLUSTER-66 -- Bela Ban Lead JGroups / Clustering Team JBoss