Regarding mentioning in the release notes. This is an understood fact -
HTTP load balancer (software) component by itself does not guarantee the
availability of the hosting m/c / process. This issue is always
addressed by mechanisms (not an exhaustive list) mentioned earlier.
Basically, software load balancer the guarantees the availability of the
application tier. You can think this too as some sort of ip binding -
incoming n/w traffic on fronting ip is mapped over different ips in the
backend.
That said, could you confirm the mechanism for ip binding - the manual
change.
glassfish_at_javadesktop.org wrote:
> oh, i did manual changes in laodbalancer..that was not a problem
> Anyways my problem is solved by interfacin a floating ip over lb IPs of bothe the servers.
> Now there is no single point of faliure.
>
> This service should acually come by default in glassfish, as of now glassfish does not support 0 point faluire HA untill and unless frontended by manual script, DNS or hardware laod balancer and they should mention it clearly in the release notes.
> [Message sent by forum member 'anzy' (anzy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=301251
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>