Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <507089706.1205776946224.JavaMail.jira@brutus>
Date: Mon, 17 Mar 2008 11:02:26 -0700 (PDT)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-3799) incorrect connect time computation
 in TimeMonitor
In-Reply-To: <25542726.1201656213903.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sangjin Lee closed GERONIMO-3799.
---------------------------------


> 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
>         Attachments: GERONIMO-3799.patch
>
>
> 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.