You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2008/01/30 02:23:33 UTC

[jira] Created: (GERONIMO-3799) incorrect connect time computation in TimeMonitor

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.

[jira] Resolved: (GERONIMO-3799) incorrect connect time computation in TimeMonitor

Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick McGuire resolved GERONIMO-3799.
------------------------------------

    Resolution: Fixed

Committed revision 616724.

Thanks Sangjin!

> 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.

[jira] Updated: (GERONIMO-3799) incorrect connect time computation in TimeMonitor

Posted by "Sangjin Lee (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sangjin Lee updated GERONIMO-3799:
----------------------------------

    Attachment: GERONIMO-3799.patch

a suggested fix

> 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.

[jira] Closed: (GERONIMO-3799) incorrect connect time computation in TimeMonitor

Posted by "Sangjin Lee (JIRA)" <ji...@apache.org>.
     [ 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.