Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <26584612.1197054105809.JavaMail.jira@brutus>
Date: Fri, 7 Dec 2007 11:01:45 -0800 (PST)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-3686) AsyncHttpClient does not reuse
 connection even if connections are persistent
In-Reply-To: <4938698.1197050143500.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-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549518 ] 

Sangjin Lee commented on GERONIMO-3686:
---------------------------------------

Yes, actually in the implementation I've written the session validation occurs inside the session cache, and not by the caller.  Agreed on the container types, that's what I've been using: ConcurrentHashMap/ConcurrentLinkedQueue.  One cannot live without them. :)

> AsyncHttpClient does not reuse connection even if connections are persistent
> ----------------------------------------------------------------------------
>
>                 Key: GERONIMO-3686
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3686
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>
> Each time AsyncHttpClient.sendRequest() is called, a new TCP connection is opened, even though connections may be kept alive per HTTP spec.  If connections are kept open, they should be reused for more requests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.