https://bz.apache.org/bugzilla/show_bug.cgi?id=69245
Jörg von Frantzius <jfrantz...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jörg von Frantzius <jfrantz...@gmail.com> ---
Thanks for pointing me to the test.
In the meantime, I found out that this was a timing problem that has to do with
sessions being reaped only every 10s, while my thinking was that it would be
more precise (e.g. with timers per session).
My test did wait for 1m + 5s, and it seems that with the SESSIONS.ser file
being present, the timing is consistently changed in a way that allowed this to
work.
When I wait for session expiry like this, it works always:
LOG.warn("Waiting 1 minute for session timeout");
try {
TimeUnit.SECONDS.sleep(60 +
tomcat.getEngine().getBackgroundProcessorDelay() * 2 + 2);
Probably the spec does not say anything about it, but a positive time-jitter of
10s-20s for session expiry was confusing at least for me.
Sorry for stealing your time!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
