RE: Session not freed in tomcat4.0.6
Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session not freed in tomcat4.0.6
Hi, Can you point me how to do these settings? Thanks, senthilnathan - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 8:24 PM Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Session not freed in tomcat4.0.6
Hi Yoav, I have noticed this behavior too. Sorry if this is a stupid question but why aren't the sessions destroyed when tomcat is shutdown? If the jvm is gone should all of it's objects be destroyed? Thanks, Paul -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:54 AM To: Tomcat Users List Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Session not freed in tomcat4.0.6
Howdy, This is not a stupid question. The servlet specification mandates that sessions be persisted across server restarts. This is done so that if a user is doing something and the server crashes, the server can come back up with the user's session data intact. When the JVM is gone, all its objects ARE gone -- from memory. Session data by default is more like preferences that are persisted. This is of course tunable: you control the session timeout (in web.xml), as well as tomcat-specific session persistence settings. Read the Manager (component, not webapp) configuration reference for details. Yoav Shapira Millennium ChemInformatics -Original Message- From: Lee, Paul NYC [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 10:01 AM To: 'Tomcat Users List' Subject: RE: Session not freed in tomcat4.0.6 Hi Yoav, I have noticed this behavior too. Sorry if this is a stupid question but why aren't the sessions destroyed when tomcat is shutdown? If the jvm is gone should all of it's objects be destroyed? Thanks, Paul -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:54 AM To: Tomcat Users List Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Session not freed in tomcat4.0.6
That's great! Thank you very much for you help. Paul -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 10:04 AM To: Tomcat Users List Subject: RE: Session not freed in tomcat4.0.6 Howdy, This is not a stupid question. The servlet specification mandates that sessions be persisted across server restarts. This is done so that if a user is doing something and the server crashes, the server can come back up with the user's session data intact. When the JVM is gone, all its objects ARE gone -- from memory. Session data by default is more like preferences that are persisted. This is of course tunable: you control the session timeout (in web.xml), as well as tomcat-specific session persistence settings. Read the Manager (component, not webapp) configuration reference for details. Yoav Shapira Millennium ChemInformatics -Original Message- From: Lee, Paul NYC [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 10:01 AM To: 'Tomcat Users List' Subject: RE: Session not freed in tomcat4.0.6 Hi Yoav, I have noticed this behavior too. Sorry if this is a stupid question but why aren't the sessions destroyed when tomcat is shutdown? If the jvm is gone should all of it's objects be destroyed? Thanks, Paul -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:54 AM To: Tomcat Users List Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session not freed in tomcat4.0.6
Can you point me how to do these settings? Change the saveOnRestart setting to false in your server.xml 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/ /Manager BTW: I didn't notice the Manager section in the server.xml file in Tomcat 5x. has it been replaced? ALSO: If I were a committer, I would vote against making the new minimal server.xml file the default for future disturbutions. It's a lot easier to instruct us newbies to uncomment something from the file than to explain how to write sections in or switch from one config file to another.. On Wednesday 03 December 2003 10:01 am, senthilnathan wrote: Hi, Can you point me how to do these settings? Thanks, senthilnathan - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 8:24 PM Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ben Souther F.W. Davison Company, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Session not freed in tomcat4.0.6
Howdy, ALSO: If I were a committer, I would vote against making the new minimal server.xml file the default for future disturbutions. It's a lot easier to instruct us newbies to uncomment something from the file than to explain how to write sections in or switch from one config file to another.. Let's stick to the subject of the thread ;) I'm not making the minimal one the default. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session not freed in tomcat4.0.6
If you notice even in 4.x the section is commented out. Also, the StandardManager is used by default unless you specify it. So, if you want different settings than the defaults, then you need to add in a Manager section with the StandardManager as the class specified. Look at the docs for specifics. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/manager.html [EMAIL PROTECTED] 12/3/03 8:24:50 AM Can you point me how to do these settings? Change the saveOnRestart setting to false in your server.xml 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/ /Manager BTW: I didn't notice the Manager section in the server.xml file in Tomcat 5x. has it been replaced? ALSO: If I were a committer, I would vote against making the new minimal server.xml file the default for future disturbutions. It's a lot easier to instruct us newbies to uncomment something from the file than to explain how to write sections in or switch from one config file to another.. On Wednesday 03 December 2003 10:01 am, senthilnathan wrote: Hi, Can you point me how to do these settings? Thanks, senthilnathan - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 8:24 PM Subject: RE: Session not freed in tomcat4.0.6 Howdy, That's not a problem. Sessions are freed (destroyed) when they are timed out. They are persisted on restart. You can control these settings via the Manager element in server.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: senthilnathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Session not freed in tomcat4.0.6 Hi, I am using Tomcat 4.0.6 in solaris2.8 After tomcat shutdown, i am seeing the sessions are not freed. I mean After shutdown and restart the tomcat, i am getting the same sessionid and the session attributes are still there. Any idea what is the problem here? Thanks, senthilnathan This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ben Souther F.W. Davison Company, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
