The problem from my point of view is that the applications are undeployed in order of its dependencies.
This will also happen to EJBs.
The last services are tomcat, cluster view and remoting. So you might reach the server in a state where is no application available.
I was thinking about writing a twiddle command to stop tomcat so that the server would not receive messages prior to being shut down. Do you know what I should stop in the JMX console to make this work?
I'd also like to run twiddle to accomplish this same goal. It doesn't appear that I can quiesce (or subsequently redirect) traffic to my nodes quickly enough to prevent message loss/error conditions upon shutdown and would love to know if there are solutions utilizing this (or any) tool.
Sorry for not responding to this thread. I did end up being able to utilize twiddle to quiesce traffic; it just took much longer than I thought it would (3-5 minutes after the initial run).