-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 9/15/2011 3:17 AM, Mark Thomas wrote:
On 14/09/2011 23:03, Christopher Schultz wrote:
John,
On 9/13/2011 5:51 AM, John Bass wrote:
In the event of a node failure, I'm assuming that there's no
way to recover from that and the failure
On 13/09/2011 10:51, John Bass wrote:
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
On 14/09/2011 23:03, Christopher Schultz wrote:
John,
On 9/13/2011 5:51 AM, John Bass wrote:
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.
Correct: no other node in the cluster can serve the
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
On 13/09/2011 10:51, John Bass wrote:
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
