In my web.xml I have

<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app xmlns="";

In a single machine clustered environment the 20 minute timeout works,
but in a two machine cluster the session does not timeout until 30 minutes..

The only difference in the single vs. two machine resin.conf is:

Single machine //Use caucho directly no ISAPI filer <http server-id="app1" host="" port="80" read-timeout="300s" write-timeout="300s"/>
//One server in cluster
       <srun server-id="app1" host="" port="6802" index="1"/>
       <web-app-deploy path="webapps"/>
//Runs in development directory
<web-app id="/xxxx" document-directory="D:/Projects/IOP/XXXX/code/web">
     <web-app id="/xxxx-help" document-directory="webapps/xxxx-help">

Two machine Cluster (No front end load balancer)
//Uses IIS via ISAPI as front end no direct access to resin configured.
       <srun server-id="app1" host="web1" port="6802" index="1"/>
       <srun server-id="app2" host="web2" port="6802" index="2"/>
   //Uses directory  with war files
    <web-app-deploy path="d:/web/apps/war-dir"/>

I couldn't tell if this issue might have been fixed my 3.1.4 or 3.0.25,
we are currently using 3.0.23.
Possibly related Issues that were fixed.

security: update form-login with session timeout issue (#1674, rep by bthakkar) session saving was still attemped after invalidation (#2031, rep by jkriesten)
timing issues with session invalidation (#1897, rep by Bradley Van Cleave)
session: update invalidation to ensure invalidation drops session (#1951)


** Robert Leland                  INTEGRITY One   Partners *
P: (703) 581-6522                       1900 Campus Commons Drive, Suite 150
F: (703) 476-7405                          Reston, VA 20191


resin-interest mailing list

Reply via email to