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.
[EMAIL PROTECTED] 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 !
