Re: Enabling Persisting Sessions Tomcat 6
Yet everywhere has said put it in the server.xml file? Dean On Tue, Aug 18, 2009 at 2:15 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Hi I have this so far yet I am confused about where it goes. The Manager element should be placed inside a Context element. The usual place for a Context element is inside a file called context.xml placed in the META-INF directory in your WAR. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: Yet everywhere has said put it in the server.xml file? Everywhere being where? The docs say nest it in a Context. Mark Dean On Tue, Aug 18, 2009 at 2:15 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Hi I have this so far yet I am confused about where it goes. The Manager element should be placed inside a Context element. The usual place for a Context element is inside a file called context.xml placed in the META-INF directory in your WAR. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: Ok ive put it in my context.xml yet the id isn't getting written in to the database. And does not persist. What have you put in which context.xml located where on your file system? And what do the logs say? Mark Dean On Wed, Aug 19, 2009 at 11:23 AM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Yet everywhere has said put it in the server.xml file? Everywhere being where? The docs say nest it in a Context. Mark Dean On Tue, Aug 18, 2009 at 2:15 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Hi I have this so far yet I am confused about where it goes. The Manager element should be placed inside a Context element. The usual place for a Context element is inside a file called context.xml placed in the META-INF directory in your WAR. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml Dean On Wed, Aug 19, 2009 at 12:20 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Ok ive put it in my context.xml yet the id isn't getting written in to the database. And does not persist. What have you put in which context.xml located where on your file system? And what do the logs say? Mark Dean On Wed, Aug 19, 2009 at 11:23 AM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Yet everywhere has said put it in the server.xml file? Everywhere being where? The docs say nest it in a Context. Mark Dean On Tue, Aug 18, 2009 at 2:15 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Hi I have this so far yet I am confused about where it goes. The Manager element should be placed inside a Context element. The usual place for a Context element is inside a file called context.xml placed in the META-INF directory in your WAR. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. I suggest you try using the real documentation rather than what appears to be an out of date book. Given that you have made some changes, what does the configuration look like now? How are you testing it? Something else to try. Start up JConsole, connect to your running Tomcat instance and look at the Manager mbeans. What value do you see for the className attribute? Mark Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Sory forgot to get rid of the session out of the cookies. It writes in to the database. Yet the session is not staying active with the client. Dean On Wed, Aug 19, 2009 at 2:47 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. I suggest you try using the real documentation rather than what appears to be an out of date book. Given that you have made some changes, what does the configuration look like now? How are you testing it? Something else to try. Start up JConsole, connect to your running Tomcat instance and look at the Manager mbeans. What value do you see for the className attribute? Mark Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: Sory forgot to get rid of the session out of the cookies. It writes in to the database. Yet the session is not staying active with the client. And if you remove the PersistentManager does it it start working again? Mark Dean On Wed, Aug 19, 2009 at 2:47 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. I suggest you try using the real documentation rather than what appears to be an out of date book. Given that you have made some changes, what does the configuration look like now? How are you testing it? Something else to try. Start up JConsole, connect to your running Tomcat instance and look at the Manager mbeans. What value do you see for the className attribute? Mark Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
No. Yet i have rewrote a test login system and that works i cannot see what is different compared to my application. On Wed, Aug 19, 2009 at 4:34 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Sory forgot to get rid of the session out of the cookies. It writes in to the database. Yet the session is not staying active with the client. And if you remove the PersistentManager does it it start working again? Mark Dean On Wed, Aug 19, 2009 at 2:47 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. I suggest you try using the real documentation rather than what appears to be an out of date book. Given that you have made some changes, what does the configuration look like now? How are you testing it? Something else to try. Start up JConsole, connect to your running Tomcat instance and look at the Manager mbeans. What value do you see for the className attribute? Mark Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: No. Yet i have rewrote a test login system and that works i cannot see what is different compared to my application. Then the problem lies in your application. LiveHttpHeaders, ieHttpHeaders, Fiddler or one of the many similar tools may prove useful to see what is going on. Mark On Wed, Aug 19, 2009 at 4:34 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Sory forgot to get rid of the session out of the cookies. It writes in to the database. Yet the session is not staying active with the client. And if you remove the PersistentManager does it it start working again? Mark Dean On Wed, Aug 19, 2009 at 2:47 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: Ok The table was table 2-8 JDBCStore attributes in Tomcat The Definitive Guide. Thats still not fixed it. I suggest you try using the real documentation rather than what appears to be an out of date book. Given that you have made some changes, what does the configuration look like now? How are you testing it? Something else to try. Start up JConsole, connect to your running Tomcat instance and look at the Manager mbeans. What value do you see for the className attribute? Mark Dean On Wed, Aug 19, 2009 at 2:07 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: I can't see your columns in the table of what is used in the element. What table? The message is all there although it is only the single attribute missing, not multiple attributes. Mark Dean On Wed, Aug 19, 2009 at 12:41 PM, Mark Thomas ma...@apache.org wrote: Dean Chester wrote: The logs are reporting nothing. And my context.xml is located $CATALINA_HOME/conf/context.xml OK. That should mean that the Manager .../ element applies to every web application. Assuming you added the Manager .../ element you originally posted... Remove the debug attribute - it doesn't do anything Remove the saveOnRestart attribute - you are using the default Your minIdleSwap, maxIdleSwap and maxIdleBackup are sufficiently large that testing will involve significant waiting. I'd reduce these to a few seconds until you get things working. Your Store element is missing the following required fields: sessionAppCol Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Enabling Persisting Sessions Tomcat 6
Hi I am wondering if someone can help me with my persisting sessions problem. I have this so far yet i am confused about where it goes, ive also created the table in the database: Manager className=org.apache.catalina.session.PersistentManager debug=0 saveOnRestart=true minIdleSwap=900 maxIdleSwap=1200 maxIdleBackup=600 Store className=org.apache.catalina.session.JDBCStore driverName=com.mysql.jdbc.Driver connectionURL=jdbc:mysql://localhost/hpsgdb connectionName=test connectionPassword=test sessionTable=tomcat_sessions sessionIdCol=session_id sessionDataCol=session_data sessionValidCol=valid_session sessionMaxInactiveCol=max_inactive sessionLastAccessedCol=last_access/ /Manager Thanks in Advance Dean
Re: Enabling Persisting Sessions Tomcat 6
Dean Chester wrote: Hi I have this so far yet I am confused about where it goes. The Manager element should be placed inside a Context element. The usual place for a Context element is inside a file called context.xml placed in the META-INF directory in your WAR. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
