https://bz.apache.org/bugzilla/show_bug.cgi?id=63324
--- Comment #3 from Konstantin Kolinko <knst.koli...@gmail.com> ---
Note that the assumption of CrawlerSessionManagerValve is that the clients does
not support cookies. Thus it forcefully assigns them to the same session based
on their IP addresses.
[[[
if (isBot) {
sessionId = clientIdSessionId.get(clientIdentifier);
]]]
1) If the client really does not support cookies, once you stop and start
Tomcat, the "clientIdSessionId" map is lost and you have lost access to those
sessions. They will never be accessed again.
They will just time out after some time elapses - "sessionInactiveInterval" in
CrawlerSessionManagerValve defaults to 60 seconds.
(Thus it makes sense to do not serialize those sessions at all, to do not
replicate them etc.
Serializing the original maps (like proposed by PR 154) does not make any
sense.)
2) If client supports cookies, you do not need a CrawlerSessionManagerValve.
Thus you not not need a value in a "clientIdSessionId" map. You will access the
session using the sessionid provided by a Cookie.
--
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
