incorrect connect time computation in TimeMonitor
-------------------------------------------------
Key: GERONIMO-3799
URL: https://issues.apache.org/jira/browse/GERONIMO-3799
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: AsyncHttpClient
Affects Versions: 1.x
Reporter: Sangjin Lee
A bug in TimeMonitor.notification() causes incorrect connect time computation.
Connect start time is set only if you're opening a new connection. If a
connection is reused, then connect start time is cleared (i.e. reset to 0).
In TimeMonitor, one should check to see connect start time is set before
recording the connect time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
