On Thu, Jun 19, 2008 at 5:42 PM, Pid <[EMAIL PROTECTED]> wrote: > André Warnier wrote: >> >> >> Leon Rosenberg wrote: >>> >>> On Thu, Jun 19, 2008 at 4:51 PM, André Warnier <[EMAIL PROTECTED]> wrote: >>> >>>> Now, maybe the issue is whether the session of one application can or >>>> cannot >>>> be valid for the other. If they just shared a session (and a cookie), >>>> then >>>> there would be harmony again. >>> >>> Or the OP just renames one of his application and all is settled again >>> :-) >>> >> But that would not change the name of the cookie, or would it ? > > The problem is that the TC1 sets a value of JSESSIONID that does not exist > in TC2. So when it visits the 2nd app, the session id it presents is not > valid.
yes > > Changing the cookie name, value or adding a port number will make no > difference. of course it would since there will be two different cookies with different pathes referring to both different sessions. wouldn't there? Leon > > AFAIK the only way to resolve this is to set up synchronous clustering on > the two instances, so that they start sharing session data. > > > p > > >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
