https://bz.apache.org/bugzilla/show_bug.cgi?id=62841
Bug ID: 62841
Summary: Refactor DeltaSession locking
Product: Tomcat 9
Version: 9.0.x
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Cluster
Assignee: dev@tomcat.apache.org
Reporter: ma...@apache.org
Target Milestone: -----
Background: https://tomcat.markmail.org/thread/26rl3hs6wjzf7ssu
It would helpful in some scenarios to reduce the scope of the DeltaSession
lock.
Currently the sequence is:
- lock session
- serialize DeltaRequest to message
- recycle DeltaRequest
- unlock session
- send message
The proposed sequence is:
- lock session
- keep reference to populated DeltaRequest
- provide session with new DeltaRequest object
- unlock session
- serialize populated DeltaRequest to message
- send message
To avoid the expense of creating a new DeltaRequest each time, a pool of them
could be used which should minimise the garbage.
Looking at the sequence of events, I don't think this does much that is
likely to harm coherence.
--
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
