RMI/ACC Fail-over failing
We currently are running Glassfish 220.127.116.11 in a 5 node cluster(for scalability) we have an application client launched via the Javaweb Start. This client connects to the glassfish server using RMI via the ACC. Everything runs really great until we run into one of these bugs(GLASSFISH-16217, GLASSFISH-18351) which causes one of the nodes to deadlock. When the node deadlocks the ACC is not smart enough to remove the deadlocked node from the list, the client freezes and becomes un-usable. Basically we have this sports car that goes really fast but we have no seatbelts or any kind of safety features. Is there anyway to change the way the ACC determines node failure so we can call our own heartbeat service or something? This is really frustrating. Any feedback would be greatly appreciated.