2 possible solutions -you could store those previously defined Session attribute values in the considerably wider Application scope -create your own SessionListener from HttpSessionListener and specify the contingency when the session is destroyed i.e. your own sessionDestroyed(HttpSessionEvent) and persist the values Take a look at http://www.velocityreviews.com/forums/t135596-detecting-session-expiration.html
Anyone else? Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "Peter Crowther" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Friday, September 22, 2006 12:04 PM Subject: RE: New session PER REQUEST > From: Darren Hall [mailto:[EMAIL PROTECTED] > I'm running a webapp built on Struts 1.2.9 running in Tomcat > 5.5 and using > an Apache 2.2 http server. I've noticed that any value I put into the > session is always removed after one request/response cycle. > In the Tomcat > Manager, I can see that every time I hit the webapp and view > a page, the > session count increments. This is terrible, as it prevents me from > persisting values across my user's session. Any idea why this would be > happening?? (I'm looking for a starting point to trouble > shoot and correct > this issue.) What happens if you connect directly to Tomcat (if necessary, set up a connector) and bypass Apache? - Peter --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
