Thank you all for your responses. We found that sticky was set up properly. The problem was with the application and how it handles clustering. Thanks again...
On Fri, Sep 21, 2012 at 11:51 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Nicolas, > > On 9/21/12 12:58 AM, Nicolas Sarazin wrote: > > Add : worker.node1.route=node1 > > > > And : worker.node2.route=node2 > > > > To use sticky session. These directives attach name route at the > > end of JSESSIONID. > > That shouldn't be necessary, as the worker's name is the default > 'route', and the OP has them set up properly. > > I think this might be interfering with your setup: > > Le vendredi 21 septembre 2012, Lou Henry a écrit : > > > >> worker.node1.domain=jvm1 worker.node2.domain=jvm2 > > Lou, do you need the "domain" for anything? The docs say that when > sticky_session=true (which is the default, and you haven't overridden > it), then the domain becomes the 'route'. Since you aren't explicitly > specifying the route, then you are probably getting implicitly: > > worker.node1.route=jvm1 > worker.node2.route=jvm2 > > when what you want is 'node1' and 'node2'. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > iEYEARECAAYFAlBdNa0ACgkQ9CaO5/Lv0PBMFwCfQZdAuuEH+FNiwli6n7+dk22B > 6/4AoIk1i4MnH3qglv8pah5xY47Jzos+ > =EA2N > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
