Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 99972 invoked by uid 500); 9 Apr 2001 10:39:49 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 99944 invoked from network); 9 Apr 2001 10:39:47 -0000 Received: from mx0.gmx.net (213.165.64.100) by h31.sny.collab.net with SMTP; 9 Apr 2001 10:39:47 -0000 Received: (qmail 7305 invoked by uid 0); 9 Apr 2001 10:40:09 -0000 Date: Mon, 9 Apr 2001 12:40:09 +0200 (MEST) From: juan.alvarez@gmx.net To: tomcat-user@jakarta.apache.org MIME-Version: 1.0 Subject: RE: Session handling over different Tomcats X-Priority: 3 (Normal) X-Authenticated-Sender: #0006859437@gmx.net X-Authenticated-IP: [194.173.184.34] Message-ID: <22517.986812809@www51.gmx.net> X-Mailer: WWW-Mail 1.5 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N We had the idea to use rmi too. We have the problem, that we are not allowed to use cookies. So we have to make an url rewrite (other ideas ?). We think that it would cost a lot of performance to make a call for every request to the session rmi. What do you think of a special apache module for adminstration of the different session ids. -----Original Message----- From: Alistair Hopkins [mailto:alistair@berthengron.co.uk] Sent: Montag, 9. April 2001 11:21 To: tomcat-user@jakarta.apache.org; moinanjum@yahoo.com Subject: RE: Session handling over different Tomcats how about running a separate login java instance on one of the boxes which can be called by all servers over RMI to check login? -----Original Message----- From: Moin Anjum H. [mailto:moinanjum@yahoo.com] Sent: Monday, April 09, 2001 10:22 AM To: tomcat-user@jakarta.apache.org Subject: Re: Session handling over different Tomcats Hi, Sound a pretty complicated problem. If you don't want to work hard i have a not a very good solution. What you can do is Keep the SessionId in the database. Apart from id keep track of the time also in the database for session timeouts. Other way i think should be able to communicate with the help of servlet chaining. Have a servlet deployed in tomcat. So there will be 4 servlet in 4 tomcats. This servlet will check the session table and return either true or false depending on the session id present in session table. One servlet will send request to other four servlet and check if the session id is present in the session table. Sound pretty complecated. HTH Moin. juan.alvarez@gmx.net wrote: > Hello, > has anyone experience in session handling over different tomcats ? > The scenario is as follows: > - one apache > - four tomcats at the apache > - every tomcat contains an application of a third party company with its own > session handling > > Problem: > Implementing a global session handling between this four applications > (single login) ! > > Any Ideas ? > > Thanks !