You are right Pid! CAS works using a Ticket Granting Cookie (which
references a Ticket Granting Ticket in an HTTP session). I assumed
that the Ticket Granting Cookie would be meaningless after the Tomcat
restart because the Ticket Granting Ticket object no longer exists on
the Server. However, that
PM
Subject: Re: How to disable Session Persistence in Tomcat 5.5.9
> Hey Charles,
>
> Thank you very much for the detailed explanation. I did the following
> to disable session persistence, but.
>
> #Tomcat\conf\server.xml
> unpackWARs="true" auto
Kristin Coles wrote:
> Hey Charles,
>
> Thank you very much for the detailed explanation. I did the following
> to disable session persistence, but.
>
> #Tomcat\conf\server.xml
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false"
> expireSessionsOnShutdown
Hey Charles,
Thank you very much for the detailed explanation. I did the following
to disable session persistence, but.
#Tomcat\conf\server.xml
I know that PersitentManager is not advisable but I got the following
message in Tomcat logs as a proof that it did di
> From: "Kristin Coles" <[EMAIL PROTECTED]>
> Subject: How to disable Session Persistence in Tomcat 5.5.9
>
> # Tomcat\conf\server.xml (version 1)
>
The above is incorrect; your appBase should be "webapps", and docBase
should be "cas". What you've specified is illegal, but is not always
detecte
Thanks for the reply Martin. However, I know about Serializable
interface and Session Timeouts.
I am using CAS (which is a huge Java open-source Single Sign-On web
application). I do not want to tamper with the original code. What
confuses me is, why do the CAS session objects remain in the sessi
"implements serializable"
Read this important article on implements Serializable from 2000
http://java.sun.com/developer/TechTips/2000/tt0229.html
And this article on Session Serialization and Session.timeout
http://java.sys-con.com/read/37330.htm
M--
- Original Message -
From: "Kristin
