2014-02-02 Maor Yosef <maoryo...@gmail.com>: > Hi, 1. 6.0.26 is old.
> We are facing issues where the sessions are not being expired > and eventually causing a stack overflow. 2. Non-expiring sessions may cause OOM, but they cannot cause a stack overflow. What are your evidences? > We see that at some point the sessions get pilled up and we need to > manually expire those sessions through the manager application, or > until we will restart tomcat but after a few hours / days, sessions > will start to get stuck again 3. Increasing count of session does not mean that sessions do not expire. Your evidence = ? > We see it in all the applications that are deployed on tomcat, > including the manager application - this rules out (in my opinion) the > possibility that its an issue with our application. 4. Sessions are expired by a background thread. If the thread is stuck somewhere (e.g. doing auto-deployment work) it will affect expiration of sessions. Your thread dump = ? By default there is one background thread that is shared by all container levels in Tomcat, but you can configure a separate one in each container (container = Context, Host or Engine). 5. Web bots that do not support cookies may generate multiple sessions. See CrawlerSessionManagerValve Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
