You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Kristin Coles <kr...@gmail.com> on 2007/11/15 01:22:37 UTC
How to disable Session Persistence in Tomcat 5.5.9
Hi guys,
I know that there have been quite a few threads on this list that
relate to the same subject. I have tried the following advice but none
helped.
# Tomcat\conf\context.xml
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<Manager pathname="" />
</Context>
# Tomcat\conf\server.xml (version 1)
<Host name="cas" appBase="webapps\cas"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false"
expireSessionsOnShutdown="true">
<Context path="" docBase="">
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="false"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"
directory="logs/sessions" />
</Manager>
</Context>
</Host>
# Tomcat\conf\server.xml (version 2)
<Host name="cas" appBase="webapps\cas"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false"
expireSessionsOnShutdown="true">
<Context path="" docBase="">
<Manager className="org.apache.catalina.session.StandardManager"
debug="0" pathname ="">
</Manager>
</Context>
</Host>
I have deployed and configured CAS (Central Authentication Service for
Single Sign-On) as as web application on Tomcat. However, while using
CAS, I've found that the user who was logged in before the Tomcat
restart, is still logged in after the Tomcat restart.
Can anyone here please help resolve this issue!!!
Thank you,
Kristin
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Kristin Coles <kr...@gmail.com>.
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 seems to be the default CAS behavior. I've
asked CAS guys for an explanation.
However this ordeal helped me learn more about Tomcat configuration.
My sincere Thanks to you and especially Charles for your prompt and
helpful answers.
Regards,
Kristin
On Nov 15, 2007 11:36 AM, Pid <p...@pidster.com> wrote:
> 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
> > <Host name="kristin" appBase="webapps"
> > unpackWARs="true" autoDeploy="true"
> > xmlValidation="false" xmlNamespaceAware="false" expireSessionsOnShutdown="true">
> > <Context path="" docBase="cas">
> > <Manager className="org.apache.catalina.session.PersistentManager"
> > debug="0" saveOnRestart="false"></Manager>
> > </Context>
> > </Host>
> >
> > I know that PersitentManager is not advisable but I got the following
> > message in Tomcat logs as a proof that it did disable session
> > pesistence....
> > [org.apache.catalina.session.PersistentManagerBase] : No Store
> > configured, persistence disabled
> >
> > HOWEVER, when I restart Tomcat and go to https://kristin/login, I
> > still get the message "You have successfully logged into the Central
> > Authentication Service."!
> >
> > I am completely stumped! Tomcat gurus please advise! Please note that
> > CAS is an application based on Spring framework.
>
> How does CAS work? Is it, for example, leaving a persistent cookie that
> is causing you to be reauthenticated?
>
> If that was the case then you could do whatever you liked with Tomcat
> sessions and it would have little or no bearing on your login status.
>
> Test this by examining your cookies.
>
>
>
> p
>
>
> > Regards,
> > Kristin
> >
> > PS: Do you guys think this is a CAS issue rather than a Tomcat one?
> >
> > PPS: Few other things that I tried are...
> > 1. Use StandardManager with pathname=""
> > 2. Removed the context and manager elements from server.xml and
> > created an individual context.xml file under Tomcat\Catalina\kristin
> > directory.
> >
> > On Nov 14, 2007 7:31 PM, Caldarale, Charles R
> > <Ch...@unisys.com> wrote:
> >>> From: "Kristin Coles" <kr...@gmail.com>
> >>> Subject: How to disable Session Persistence in Tomcat 5.5.9
> >>>
> >>> # Tomcat\conf\server.xml (version 1)
> >>> <Host name="cas" appBase="webapps\cas"
> >>> <Context path="" docBase="">
> >> The above is incorrect; your appBase should be "webapps", and docBase
> >> should be "cas". What you've specified is illegal, but is not always
> >> detected.
> >>
> >>> <Manager className="org.apache.catalina.session.PersistentManager"
> >> As the doc states, the PersistentManager is not ready for prime time -
> >> you really don't want to mess with it.
> >>
> >> By specifying a <Manager> element inside the <Context>, you override the
> >> one in conf/context.xml, thereby rendering your previous configuration
> >> useless.
> >>
> >>> # Tomcat\conf\server.xml (version 2)
> >>> <Host name="cas" appBase="webapps\cas"
> >>> <Context path="" docBase="">
> >> Same comment as above.
> >>
> >>> <Manager className="org.apache.catalina.session.StandardManager"
> >>> debug="0" pathname ="">
> >> Is that a typo, or do you really have an extra space after pathname?
> >>
> >> Note that placing <Context> elements in server.xml is strongly
> >> discouraged these days; you might want to consider one of the standard
> >> locations, and get rid of the path and docBase attributes. If you want
> >> cas to be the default app, simply name it ROOT.
> >>
> >> Fix the obvious errors, and then let's see what happens.
> >>
> >> - Chuck
> >>
> >>
> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> >> MATERIAL and is thus for use only by the intended recipient. If you
> >> received this in error, please contact the sender and delete the e-mail
> >> and its attachments from all computers.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Pid <p...@pidster.com>.
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
> <Host name="kristin" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false" expireSessionsOnShutdown="true">
> <Context path="" docBase="cas">
> <Manager className="org.apache.catalina.session.PersistentManager"
> debug="0" saveOnRestart="false"></Manager>
> </Context>
> </Host>
>
> I know that PersitentManager is not advisable but I got the following
> message in Tomcat logs as a proof that it did disable session
> pesistence....
> [org.apache.catalina.session.PersistentManagerBase] : No Store
> configured, persistence disabled
>
> HOWEVER, when I restart Tomcat and go to https://kristin/login, I
> still get the message "You have successfully logged into the Central
> Authentication Service."!
>
> I am completely stumped! Tomcat gurus please advise! Please note that
> CAS is an application based on Spring framework.
How does CAS work? Is it, for example, leaving a persistent cookie that
is causing you to be reauthenticated?
If that was the case then you could do whatever you liked with Tomcat
sessions and it would have little or no bearing on your login status.
Test this by examining your cookies.
p
> Regards,
> Kristin
>
> PS: Do you guys think this is a CAS issue rather than a Tomcat one?
>
> PPS: Few other things that I tried are...
> 1. Use StandardManager with pathname=""
> 2. Removed the context and manager elements from server.xml and
> created an individual context.xml file under Tomcat\Catalina\kristin
> directory.
>
> On Nov 14, 2007 7:31 PM, Caldarale, Charles R
> <Ch...@unisys.com> wrote:
>>> From: "Kristin Coles" <kr...@gmail.com>
>>> Subject: How to disable Session Persistence in Tomcat 5.5.9
>>>
>>> # Tomcat\conf\server.xml (version 1)
>>> <Host name="cas" appBase="webapps\cas"
>>> <Context path="" docBase="">
>> The above is incorrect; your appBase should be "webapps", and docBase
>> should be "cas". What you've specified is illegal, but is not always
>> detected.
>>
>>> <Manager className="org.apache.catalina.session.PersistentManager"
>> As the doc states, the PersistentManager is not ready for prime time -
>> you really don't want to mess with it.
>>
>> By specifying a <Manager> element inside the <Context>, you override the
>> one in conf/context.xml, thereby rendering your previous configuration
>> useless.
>>
>>> # Tomcat\conf\server.xml (version 2)
>>> <Host name="cas" appBase="webapps\cas"
>>> <Context path="" docBase="">
>> Same comment as above.
>>
>>> <Manager className="org.apache.catalina.session.StandardManager"
>>> debug="0" pathname ="">
>> Is that a typo, or do you really have an extra space after pathname?
>>
>> Note that placing <Context> elements in server.xml is strongly
>> discouraged these days; you might want to consider one of the standard
>> locations, and get rid of the path and docBase attributes. If you want
>> cas to be the default app, simply name it ROOT.
>>
>> Fix the obvious errors, and then let's see what happens.
>>
>> - Chuck
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you
>> received this in error, please contact the sender and delete the e-mail
>> and its attachments from all computers.
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Martin Gainty <mg...@hotmail.com>.
this *may help*..
http://forums.atlassian.com/thread.jspa?messageID=257247254
<!--in $TOMCAT_HOME/conf/context.xml.. Uncomment this to disable session
persistence across Tomcat restarts -->
<Manager pathname="" />
M--
assumption is you're not using hibernate?
----- Original Message -----
From: "Kristin Coles" <kr...@gmail.com>
To: "Tomcat Users List" <us...@tomcat.apache.org>
Sent: Thursday, November 15, 2007 12:54 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
> <Host name="kristin" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false"
expireSessionsOnShutdown="true">
> <Context path="" docBase="cas">
> <Manager className="org.apache.catalina.session.PersistentManager"
> debug="0" saveOnRestart="false"></Manager>
> </Context>
> </Host>
>
> I know that PersitentManager is not advisable but I got the following
> message in Tomcat logs as a proof that it did disable session
> pesistence....
> [org.apache.catalina.session.PersistentManagerBase] : No Store
> configured, persistence disabled
>
> HOWEVER, when I restart Tomcat and go to https://kristin/login, I
> still get the message "You have successfully logged into the Central
> Authentication Service."!
>
> I am completely stumped! Tomcat gurus please advise! Please note that
> CAS is an application based on Spring framework.
>
> Regards,
> Kristin
>
> PS: Do you guys think this is a CAS issue rather than a Tomcat one?
>
> PPS: Few other things that I tried are...
> 1. Use StandardManager with pathname=""
> 2. Removed the context and manager elements from server.xml and
> created an individual context.xml file under Tomcat\Catalina\kristin
> directory.
>
> On Nov 14, 2007 7:31 PM, Caldarale, Charles R
> <Ch...@unisys.com> wrote:
> > > From: "Kristin Coles" <kr...@gmail.com>
> > > Subject: How to disable Session Persistence in Tomcat 5.5.9
> > >
> > > # Tomcat\conf\server.xml (version 1)
> > > <Host name="cas" appBase="webapps\cas"
> > > <Context path="" docBase="">
> >
> > The above is incorrect; your appBase should be "webapps", and docBase
> > should be "cas". What you've specified is illegal, but is not always
> > detected.
> >
> > > <Manager className="org.apache.catalina.session.PersistentManager"
> >
> > As the doc states, the PersistentManager is not ready for prime time -
> > you really don't want to mess with it.
> >
> > By specifying a <Manager> element inside the <Context>, you override the
> > one in conf/context.xml, thereby rendering your previous configuration
> > useless.
> >
> > > # Tomcat\conf\server.xml (version 2)
> > > <Host name="cas" appBase="webapps\cas"
> > > <Context path="" docBase="">
> >
> > Same comment as above.
> >
> > > <Manager className="org.apache.catalina.session.StandardManager"
> > > debug="0" pathname ="">
> >
> > Is that a typo, or do you really have an extra space after pathname?
> >
> > Note that placing <Context> elements in server.xml is strongly
> > discouraged these days; you might want to consider one of the standard
> > locations, and get rid of the path and docBase attributes. If you want
> > cas to be the default app, simply name it ROOT.
> >
> > Fix the obvious errors, and then let's see what happens.
> >
> > - Chuck
> >
> >
> > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> > MATERIAL and is thus for use only by the intended recipient. If you
> > received this in error, please contact the sender and delete the e-mail
> > and its attachments from all computers.
> >
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Kristin Coles <kr...@gmail.com>.
Hey Charles,
Thank you very much for the detailed explanation. I did the following
to disable session persistence, but.....
#Tomcat\conf\server.xml
<Host name="kristin" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" expireSessionsOnShutdown="true">
<Context path="" docBase="cas">
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0" saveOnRestart="false"></Manager>
</Context>
</Host>
I know that PersitentManager is not advisable but I got the following
message in Tomcat logs as a proof that it did disable session
pesistence....
[org.apache.catalina.session.PersistentManagerBase] : No Store
configured, persistence disabled
HOWEVER, when I restart Tomcat and go to https://kristin/login, I
still get the message "You have successfully logged into the Central
Authentication Service."!
I am completely stumped! Tomcat gurus please advise! Please note that
CAS is an application based on Spring framework.
Regards,
Kristin
PS: Do you guys think this is a CAS issue rather than a Tomcat one?
PPS: Few other things that I tried are...
1. Use StandardManager with pathname=""
2. Removed the context and manager elements from server.xml and
created an individual context.xml file under Tomcat\Catalina\kristin
directory.
On Nov 14, 2007 7:31 PM, Caldarale, Charles R
<Ch...@unisys.com> wrote:
> > From: "Kristin Coles" <kr...@gmail.com>
> > Subject: How to disable Session Persistence in Tomcat 5.5.9
> >
> > # Tomcat\conf\server.xml (version 1)
> > <Host name="cas" appBase="webapps\cas"
> > <Context path="" docBase="">
>
> The above is incorrect; your appBase should be "webapps", and docBase
> should be "cas". What you've specified is illegal, but is not always
> detected.
>
> > <Manager className="org.apache.catalina.session.PersistentManager"
>
> As the doc states, the PersistentManager is not ready for prime time -
> you really don't want to mess with it.
>
> By specifying a <Manager> element inside the <Context>, you override the
> one in conf/context.xml, thereby rendering your previous configuration
> useless.
>
> > # Tomcat\conf\server.xml (version 2)
> > <Host name="cas" appBase="webapps\cas"
> > <Context path="" docBase="">
>
> Same comment as above.
>
> > <Manager className="org.apache.catalina.session.StandardManager"
> > debug="0" pathname ="">
>
> Is that a typo, or do you really have an extra space after pathname?
>
> Note that placing <Context> elements in server.xml is strongly
> discouraged these days; you might want to consider one of the standard
> locations, and get rid of the path and docBase attributes. If you want
> cas to be the default app, simply name it ROOT.
>
> Fix the obvious errors, and then let's see what happens.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: How to disable Session Persistence in Tomcat 5.5.9
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: "Kristin Coles" <kr...@gmail.com>
> Subject: How to disable Session Persistence in Tomcat 5.5.9
>
> # Tomcat\conf\server.xml (version 1)
> <Host name="cas" appBase="webapps\cas"
> <Context path="" docBase="">
The above is incorrect; your appBase should be "webapps", and docBase
should be "cas". What you've specified is illegal, but is not always
detected.
> <Manager className="org.apache.catalina.session.PersistentManager"
As the doc states, the PersistentManager is not ready for prime time -
you really don't want to mess with it.
By specifying a <Manager> element inside the <Context>, you override the
one in conf/context.xml, thereby rendering your previous configuration
useless.
> # Tomcat\conf\server.xml (version 2)
> <Host name="cas" appBase="webapps\cas"
> <Context path="" docBase="">
Same comment as above.
> <Manager className="org.apache.catalina.session.StandardManager"
> debug="0" pathname ="">
Is that a typo, or do you really have an extra space after pathname?
Note that placing <Context> elements in server.xml is strongly
discouraged these days; you might want to consider one of the standard
locations, and get rid of the path and docBase attributes. If you want
cas to be the default app, simply name it ROOT.
Fix the obvious errors, and then let's see what happens.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Kristin Coles <kr...@gmail.com>.
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 session
even when I made the necessary changes to the Tomcat config files and
restarted Tomcat.
Thank you!
Kristin
On Nov 14, 2007 5:46 PM, Martin Gainty <mg...@hotmail.com> wrote:
> "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 Coles" <kr...@gmail.com>
> To: <us...@tomcat.apache.org>
> Sent: Wednesday, November 14, 2007 7:22 PM
> Subject: How to disable Session Persistence in Tomcat 5.5.9
>
>
> > Hi guys,
> >
> > I know that there have been quite a few threads on this list that
> > relate to the same subject. I have tried the following advice but none
> > helped.
> >
> > # Tomcat\conf\context.xml
> > <Context>
> > <WatchedResource>WEB-INF/web.xml</WatchedResource>
> > <Manager pathname="" />
> > </Context>
> >
> > # Tomcat\conf\server.xml (version 1)
> > <Host name="cas" appBase="webapps\cas"
> > unpackWARs="true" autoDeploy="true"
> > xmlValidation="false" xmlNamespaceAware="false"
> > expireSessionsOnShutdown="true">
> > <Context path="" docBase="">
> > <Manager className="org.apache.catalina.session.PersistentManager"
> > debug="0"
> > saveOnRestart="false"
> > maxActiveSessions="-1"
> > minIdleSwap="-1"
> > maxIdleSwap="-1"
> > maxIdleBackup="-1">
> > <Store className="org.apache.catalina.session.FileStore"
> > directory="logs/sessions" />
> > </Manager>
> > </Context>
> > </Host>
> >
> > # Tomcat\conf\server.xml (version 2)
> > <Host name="cas" appBase="webapps\cas"
> > unpackWARs="true" autoDeploy="true"
> > xmlValidation="false" xmlNamespaceAware="false"
> > expireSessionsOnShutdown="true">
> > <Context path="" docBase="">
> > <Manager className="org.apache.catalina.session.StandardManager"
> > debug="0" pathname ="">
> > </Manager>
> > </Context>
> > </Host>
> >
> > I have deployed and configured CAS (Central Authentication Service for
> > Single Sign-On) as as web application on Tomcat. However, while using
> > CAS, I've found that the user who was logged in before the Tomcat
> > restart, is still logged in after the Tomcat restart.
> >
> > Can anyone here please help resolve this issue!!!
> >
> > Thank you,
> > Kristin
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to disable Session Persistence in Tomcat 5.5.9
Posted by Martin Gainty <mg...@hotmail.com>.
"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 Coles" <kr...@gmail.com>
To: <us...@tomcat.apache.org>
Sent: Wednesday, November 14, 2007 7:22 PM
Subject: How to disable Session Persistence in Tomcat 5.5.9
> Hi guys,
>
> I know that there have been quite a few threads on this list that
> relate to the same subject. I have tried the following advice but none
> helped.
>
> # Tomcat\conf\context.xml
> <Context>
> <WatchedResource>WEB-INF/web.xml</WatchedResource>
> <Manager pathname="" />
> </Context>
>
> # Tomcat\conf\server.xml (version 1)
> <Host name="cas" appBase="webapps\cas"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false"
> expireSessionsOnShutdown="true">
> <Context path="" docBase="">
> <Manager className="org.apache.catalina.session.PersistentManager"
> debug="0"
> saveOnRestart="false"
> maxActiveSessions="-1"
> minIdleSwap="-1"
> maxIdleSwap="-1"
> maxIdleBackup="-1">
> <Store className="org.apache.catalina.session.FileStore"
> directory="logs/sessions" />
> </Manager>
> </Context>
> </Host>
>
> # Tomcat\conf\server.xml (version 2)
> <Host name="cas" appBase="webapps\cas"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false"
> expireSessionsOnShutdown="true">
> <Context path="" docBase="">
> <Manager className="org.apache.catalina.session.StandardManager"
> debug="0" pathname ="">
> </Manager>
> </Context>
> </Host>
>
> I have deployed and configured CAS (Central Authentication Service for
> Single Sign-On) as as web application on Tomcat. However, while using
> CAS, I've found that the user who was logged in before the Tomcat
> restart, is still logged in after the Tomcat restart.
>
> Can anyone here please help resolve this issue!!!
>
> Thank you,
> Kristin
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org