-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew,
Andrew Hole wrote: > I've two tomcat instantes and an apache web server with mod_jk. Mod_jk > balance request to each tomcat. > Think on following situation; > - TomcatA and TomcatB up > - I make a request to Apache that redirects to TomcatA. I'm editing text on > JSP (lot of input texts). In this moment TomcatA craches. > What's happen when I click on submit button? The behavior largely depends upon what else you have set up. First, is your application statefull -- that is, do you need the visitor's HTTP session to stick around and store information that is not provided in the request? Second, does your application require authentication -- a username and password? If either of these is true, you will have to make some kind of arrangements for fail-over. If you just need authentication, then your users can probably tolerate a re-login if they switch from TomcatA to TomcatB; their original request (form submission) will be processed after successful authentication. If you store a ton of information in the session, you might have to use session replication to ensure that the data is on all servers in the cluster /before/ a failure occurs. > What you suggest to solve this situation? Personally, I prefer reasonably stateless applications because you don't have to worry about replication or any of those things. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG7o0b9CaO5/Lv0PARAnTeAJ9OP6r5WsanhwAHT+hHPCfU5/sE5gCfdsNj GnrtC/6dL/8ev29HMoTyTk4= =hGC3 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
