Hello,
Tomcat 4.1.12, running with JBoss 3.0.4 on RedHat 8.0, seems to be holding
onto sessions between deployments of a webapp. With the old version
(3.something) the sessions would get killed when the app was redeployed. But
now I have to shutdown tomcat, redeploy the app, and then restart
Baker, Derek [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hello,
Tomcat 4.1.12, running with JBoss 3.0.4 on RedHat 8.0, seems to be holding
onto sessions between deployments of a webapp. With the old version
(3.something) the sessions would get killed when
Morning
Nope, Tomcat 4.1.x will hang onto the sessions. And the even worse news is
that Tomcat 3.3.2-dev will now hang onto the sessions across a
context-reload :).
This is not the behaviour I see.Sessions are invalidated after an ant
reload on tomcat 4.1.12-LE on a semislackware install