I said right off it was flawed didn't I? :)
Only benefit to it is it's dynamic. But, I suppose if people want things to be
completely dynamic they shouldn't expect this kind of functionality. They should be
using redundant power supplies, IP bonding and redundant networks.
Re: disabling access if this occurs, there's no standard HTTP status code (e.g. 410)
to tell a load balancer to fail over. All the HTTP status codes propagate to the client.
With mod_jk, they're working on a much more rich communication between the Tomcat side
and the Apache side, so all sorts of status information about the cluster could be passed.
With other load balancers from major vendors we could send a custom HTTP header; we'd
need to coordinate with the vendors to get them to understand the header. If none of
those options are available, we'd have to shut down the connector.
I want to have pluggable policies for configuring this kind of thing. An expansion on the
existing "useJK" flag.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084536#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...