https://bz.apache.org/bugzilla/show_bug.cgi?id=66513
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #9 from Mark Thomas <ma...@apache.org> ---
This bug is heading towards being resolved as WONTFIX.
For a long explanation see https://markmail.org/message/5gtpirnouqfraw6w
The short version is that while we can construct a solution to ensure no more
than one concurrent request per session on a single Tomcat node, we can't do it
across multiple nodes.
Given we can't fix the multiple node issue we have to rely on the clients not
issuing more than one concurrent request per session. If the clients break that
guarantee, stuff will break.
Is the PersistenceValve still useful in these circumstances?
Re-reading this issue, you mention both using this with containers plus
non-sticky load-balancing and with a single node. What is the use case for a
single node?
Is there any benefit to Tomcat guaranteeing no more than one concurrent request
per session for a single node. If so, how and why is that a benefit for your
use case?
--
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
