Hi all, I'm relatively new to clustering with Tomcat and I'm trying to understand the edge cases. If I'd like to guarantee continuous availability, what are the caveats?
As I understand it, Tomcat clustering will ensure that session information is persisted in the event of a failure. That's fine, however, what about long running I/O operations? What if my node dies in the middle of serving an HTTP response? In the event of a node failure, I'm assuming that there's no way to recover from that and the failure will be visible to a client application. Similarly, if a node fails during a long running calculation, I'm assuming that there's no way to persist that execution state. Are those assumptions correct? If anyone has any other comments on further scenarios where clustering and session persistence will not be useful in an HA context, i'd love to hear them. thanks, John
