Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of rickmcg@gmail.com designates
 209.85.198.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=bT3CXDmTmlyInbArosywhu8kd/TJ2hBavUkrglX/IV/jF5e6+56VKN5m8VDE03i3y4t92Z000+/0I/HUAkvA2rg4P/bLSg8XJDlMLgFYGnQKMVRFcpAheFK6VEvAQW6uasQJdZTz4t+m0lyAyVCldKMHS20u6m3ehjtShejLWjI=
Message-ID: <478BB139.3060000@gmail.com>
Date: Mon, 14 Jan 2008 14:00:09 -0500
From: Rick McGuire <rickmcg@gmail.com>
Reply-To: rickmcg@gmail.com
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Geronimo Dev <dev@geronimo.apache.org>
Subject: Is there a problem with AsyncHttpClient connection reuse?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I haven't convinced myself that this is a problem yet, but it's worth 
asking the question.  The AsyncHttpClient has support for connection 
reuse when making repeated connections to sites.  Since these 
connnections persist between instantiations of AsyncHttpClient 
instances, there's a single static cache of the reusable connections 
that is maintained.  Selection from the session cache is made using the 
host/port combination only, which means it's possible that a connection 
that is reused by a client will get processed using the thread pool 
configuration of the original connection client and not the current 
requesting client.  I suspect this is not an issue that can be that can 
be easily detected or protected against, so the "fix" might just be a 
word of caution added to the documentation on enabling connection reuse.

rick