I am using the AsyncClient (4.0-beta1) as part of an HTTP workload driver,
along with HttpCore 4.2.1 and HttpClient 4.2.1. My primary entry-point is
through calls to
I am having trouble sending an HttpEntity created using the
MultipartEntityBuilder on the HttpAsyncClient.
Based on this exchange from the httpclient-users mailing list:
http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201206.mbox/%3c1339240012.2405.12.camel@ubuntu%3e
I thought
-
From: Harold Rosenberg hrose...@vmware.com
To: httpclient-users@hc.apache.org
Sent: Friday, November 8, 2013 12:38:10 PM
Subject: HttpAsyncClient with MultipartEnityBuilder
I am having trouble sending an HttpEntity created using the
MultipartEntityBuilder on the HttpAsyncClient.
Based
, 2013-11-08 at 09:45 -0800, Harold Rosenberg wrote:
Actually, one minor correction. In the second case, the exception stack is
actually slightly different. It is:
The mpEntity isRepeatable = true
Exception in thread main java.lang.UnsupportedOperationException: Multipart
form entity does
At one point I was having this same issue. After some debugging I
realized that I was reusing a HttpContext for multiple concurrent
operations even though the HttpContext is not thread safe (see
https://hc.apache.org/httpcomponents-core-4.3.x/httpcore/apidocs/org/apache
I am seeing unexpected behavior in the memory usage of a program that uses the
Async Http Client. The issue arises when I switch from using exclusively HTTP
connections to exclusively HTTPS connections. In the latter case, there is a
large amount of memory used for byte arrays that seem to be
(about 3GB of live data
for a run with 15,000 simulated users), but that is to be expected.
Thanks for the help.
Hal
On 3/23/16, 3:59 PM, "Oleg Kalnichevski" <ol...@apache.org> wrote:
>On Wed, 2016-03-23 at 18:54 +0000, Harold Rosenberg wrote:
>> I am seeing unexpect
