-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review LeakDetector & LeakTrackingConnectionPool #4949
Comments
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has been a |
This issue has been automatically marked as stale because it has been a |
This issue has been automatically marked as stale because it has been a |
Removed in 561fd31. |
Jetty version
9.4.x
Description
Review
LeakDetector
to see if it's modern enough.Also, try to make
LeakTrackingConnectionPool
use delegation rather than inheritance, following the model ofLeakTrackingByteBufferPool
.See also #2814 for a description of the problems that
LeakTrackingConnectionPool
has due to the fact that uses delegation.Benchmark the cost of the leak detector to see how expensive it is, to suggest whether it's fine to use it in "production" code or not.
The text was updated successfully, but these errors were encountered: