On 21/07/2021 15:34, Ivano Luberti wrote:
Hello, I'm new to the list but befeore writing this I have searched the
users mailing list without finding anything useful.
I have an instance of Apache Tomcat/8.5.57 running on a CentOS machine
with java 1.7.0_261
Several webapps run on this instance.
I have noticed that after a few days tomcat stops killing expired sessions.
Trying to understand where the issue is located , I have enabled debug
logging of org.apache.catalina.session package with:
java.util.logging.ConsoleHandler.level = FINEST
org.apache.catalina.session.level = FINEST
So after the latest restart i could observe in catalina.out many log
rows like
21-Jul-2021 10:02:00.702 FINE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.session.ManagerBase.processExpires Start expire
sessions StandardManager at 1626861720702 sessioncount 1
21-Jul-2021 10:02:00.702 FINE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.session.ManagerBase.processExpires End expire
sessions StandardManager processingTime 0 expired sessions: 0
Today, after 4 days without issues tomcat stopped again killing expired
sessions and at the same time no more logs of
org.apache.catalina.session.ManagerBase.processExpires
are reported.
There is no other related log event , simply the last row reported is
21-Jul-2021 12:38:39.370 FINE
[ContainerBackgroundProcessor[StandardEngine[Catalina]]]
org.apache.catalina.session.ManagerBase.processExpires Start expire
sessions StandardManager at 1626871119370 sessioncount 7
Any clue on why org.apache.catalina.session.ManagerBase is not called
anymore?
Deadlock during background processing maybe?
Suggestion on how to diagnose?
Take 3 thread dumps 5 seconds apart and post them here.
Any chance that some exception occurring in
HttpSessionListener.sessionCreated
or
HttpSessionListener.sessionDestroyed
or
HttpSessionBindingListener.valueBound
or
HttpSessionBindingListener.valueUnbound
can terminate ManagerBase but without generating any logging?
Not that I can see. If the thread fails, it should be automatically
restarted. An OOME might be able to trigger this but that looks pretty
far fetched at this point.
Those are the only interaction with session handling I'm aware of.
I have the same webapps running on other tomcat instances, but on older
tomcat version and there I have no issue of ths kind.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
