Hi,
Please let me know of your requirement for application fail-over. I may
be able to provide some solution.
As of now if application is undeployed, then load-balancer xml should be
updated. You can use admin ease-of-use feature to automatically update
the load-balancer xml if cluster is modified, via application
deployment/undeployment etc.
You can also try multiple clusters to create heterogeneous deployment of
applications. Say deploy application1 and application2 on cluster1,
while deploying application2 and application3 on cluster2. So
application1 is load-balanced only to cluster1, application3 is
load-balanced only to cluster2 while application2 is load-balanced to
both cluster1 and cluster2. In case you undeploy application2 from
cluster1, cluster2 will take care of servicing request for application2.
However remember session fail-over is restricted to cluster boundary.
Thanks,
Kshitiz
glassfish_at_javadesktop.org wrote:
> In That Case can you please explain how lb takes care of failover at application level ?
> Let us say out of several applications running on a cluster one of them goes down..(due to any x,y ,z reasons) or is not available . What health check does lb performa at application level if it is not able to make out the state of application ?
>
> Whose responsibility is it to update loadbalancerxml with the unhealthy state of application when niether is Appserver nor the Webserver is aware of it ?
>
> All it can manage is a complete instance .. is that it ?
> [Message sent by forum member 'anzy' (anzy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=322606
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>