Re: Async client and gzip request : UnsupportedOperationException

On Thu, 2018-07-19 at 13:55 +0200, Gabriel Landais wrote: > Hi, > my scenario : > > 1. create an entity with an EntityBuilder and use > EntityBuilder.gzipCompress() > (it will create a GzipCompressingEntity) > 2. set entity on a compatible HttpUriRequest (HttpPost for instance) > 3. execute this

Async client and gzip request : UnsupportedOperationException

Hi, my scenario : 1. create an entity with an EntityBuilder and use EntityBuilder.gzipCompress() (it will create a GzipCompressingEntity) 2. set entity on a compatible HttpUriRequest (HttpPost for instance) 3. execute this request on a HttpAsyncClient 4. EntityAsyncContentProducer.produceContent

RE: Async client with self signed certificate

Hi, Yes, you were right, the keystore didin't have the server's public certificate. Thanks, Joan. -Mensaje original- De: Hassan Khan [mailto:hassankhan...@gmail.com] Enviado el: jueves, 18 de mayo de 2017 21:08 Para: HttpClient User Discussion Asunto: Re: Async client with self signed

Re: Async client with self signed certificate

You can remove most of this boilerplate if use use the SslContextBuilder class. Gary On May 18, 2017 11:48 AM, "Joan Balagueró" wrote: > Hello, > > > > I’ve been using SSL with client authentication with signed certificates in > async http client 4.1, with no

Re: Async client with self signed certificate

Hi, This is a issue with the CA certs... SSL handshake is failing... if java turn on ssl debug... you will see the error in detail... But if you have added the cacert to the java cacert files.. then java should recognize the self signed cert.. This is not a code issue.. it more to do with cert

Async client with self signed certificate

Hello, I’ve been using SSL with client authentication with signed certificates in async http client 4.1, with no problem. My code is: FileInputStream fKeyStore = new FileInputStream(new File(keyStoreLocation)); KeyStore keyStore = KeyStore.getInstance(keyStoreType);

Re: NoHttpResponseException in the async client

On Thu, 2016-11-10 at 11:31 +0100, Joan Balagueró - ventusproxy wrote: > Hello, > > We have replaced the httpclient by the async client in our application. > Everything works fine, but the ‘NoHttpResponseException’ has disappeared > from our error statistics reports. So, or wit

NoHttpResponseException in the async client

Hello, We have replaced the httpclient by the async client in our application. Everything works fine, but the ‘NoHttpResponseException’ has disappeared from our error statistics reports. So, or with the new async pool this error does not occur for some reason (that I don’t know) or we

NoHttpResponseException in the async client

Hello, We have replaced the httpclient by the async client in our application. Everything works fine, but the ‘NoHttpResponseException’ has disappeared from our error statistics reports. So, or with the new async pool this error does not occur for some reason (that I don’t know) or we

RE: java.util.concurrent.TimeoutException with the async client

Hi Oleg, > 1. Why, exactly in the same load conditions, a pool with 600 connections is > more than enough for the blocking client and not enough for the async one? > I cannot answer this question unless I can analyze and re-run the benchmark used to load test both clients. --> ok, I'll retest

Re: java.util.concurrent.TimeoutException with the async client

On Thu, 2016-10-27 at 15:13 +0200, Joan Balagueró wrote: > Hi Oleg, > > Sorry yes, reviewing emails I already asked about TimeoutException. I've been > reading again the httpcore tutorial because think I had a misunderstanding > about how the async client works. > > In the

RE: java.util.concurrent.TimeoutException with the async client

Hi Oleg, Sorry yes, reviewing emails I already asked about TimeoutException. I've been reading again the httpcore tutorial because think I had a misunderstanding about how the async client works. In the previous case we had about 1000 requests per second, and the average response time

Re: java.util.concurrent.TimeoutException with the async client

On Thu, 2016-10-27 at 12:23 +0200, Joan Balagueró wrote: > Hello, > > After working in production with the async client (instead of the blocking > one) everything seems ok, except that now I can see this error > intermitently: > > java.util.concur

RE: java.util.concurrent.TimeoutException with the async client

with the async client Hello, After working in production with the async client (instead of the blocking one) everything seems ok, except that now I can see this error intermitently: java.util.concurrent.TimeoutException at org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest

java.util.concurrent.TimeoutException with the async client

Hello, After working in production with the async client (instead of the blocking one) everything seems ok, except that now I can see this error intermitently: java.util.concurrent.TimeoutException at org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest(AbstractN

Re: Retries with the async client

On Wed, 2016-09-21 at 13:51 +0200, Joan Balagueró wrote: > Hello, > > I’m trying to retry ‘NoHttpResponse’ exceptions with the async client. The > point is I’m unable to generate this kind of error from my server. So my > question is: does this kind of exceptions that can b

Retries with the async client

Hello, I’m trying to retry ‘NoHttpResponse’ exceptions with the async client. The point is I’m unable to generate this kind of error from my server. So my question is: does this kind of exceptions that can be retried reach the callback? In my case the HttpAsyncResponseConsumer.responseReceived

Re: Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

; > > Thanks for your responses. When the client sends the POST request, we are > > > sending the Content-Length to the correct value. Since the client is > > using > > > a duplex channel to write/read data, why would the server sending 201 > > cause > > >

Re: Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

; sending the Content-Length to the correct value. Since the client is > using > > a duplex channel to write/read data, why would the server sending 201 > cause > > any issues with client writing all the data? Shouldn't the client make > sure > > that it is writing all th

Re: Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

? Shouldn't the client make sure that it is writing all the data corresponding to Content-Length? Is the async client aborting request explicitly? I would like to add that the same server can successfully talk to a browser without any issues with similar request payload. We also made sure that we were

Re: Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

did not do a good job of explaining > the problem that I am facing. My sincere apologies for that. > > We have a custom server that my client Java application is communicating > with using the async client. To be specific we are using an instance of > CloseableHttpAsyncClient from the

Re: Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

that. > > We have a custom server that my client Java application is communicating > with using the async client. To be specific we are using an instance of > CloseableHttpAsyncClient from the client application. The client sends a > POST request with few kilo bytes of data. The server

Can a 201 (Created) response cause HTTP async client to prematurely send a FIN to the server?

Hi all, I realized that in my previous post, I did not do a good job of explaining the problem that I am facing. My sincere apologies for that. We have a custom server that my client Java application is communicating with using the async client. To be specific we are using an instance

Re: Heap usage issue in Async Client

On Thu, 2016-03-24 at 12:26 +, Harold Rosenberg wrote: > Using the ReleasableSSLBufferManagementStrategy gave a nice improvement. For > the same run with 7500 simulated users, the change reduced the average live > data in the heap after a full GC from 3.2GB to about 1.5GB. The amount of >

Re: Heap usage issue in Async Client

Using the ReleasableSSLBufferManagementStrategy gave a nice improvement. For the same run with 7500 simulated users, the change reduced the average live data in the heap after a full GC from 3.2GB to about 1.5GB. The amount of live data is still proportional to the number of connections

Re: Heap usage issue in Async Client

On Wed, 2016-03-23 at 18:54 +, Harold Rosenberg wrote: > 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

Heap usage issue in Async Client

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

RE: Help with async client

es can be really large and I always need to store them in memory for further processing? Thanks, Joan. -Mensaje original- De: Oleg Kalnichevski [mailto:ol...@apache.org] Enviado el: jueves, 17 de marzo de 2016 10:50 Para: HttpClient User Discussion Asunto: Re: Help with async client On Thu, 2

RE: Help with async client

to get the IOReactor config from the nio pool. Thanks, Joan. -Mensaje original- De: Oleg Kalnichevski [mailto:ol...@apache.org] Enviado el: miércoles, 16 de marzo de 2016 16:22 Para: HttpClient User Discussion Asunto: Re: Help with async client On Wed, 2016-03-16 at 15:41 +0100, Joan

Re: Help with async client

On Wed, 2016-03-16 at 15:41 +0100, Joan Balagueró wrote: > Hi Oleg, > > Finally the issue was nothing to do with the async client. > > Now we are experimenting with connection and response timeouts, setting just > 1ms for both. In the blocking client, we get connection and

Re: Help with async client

On Thu, 2016-03-17 at 10:42 +0100, Joan Balagueró wrote: > Hi Oleg, > > Thanks. If I have a 400ms connection timeout and a 850ms response timeout, I > understand that the select interval must contain the 400ms (the lowest > value). True? > Yes. > In our app these connection/response timeouts

RE: Help with async client

Hi Oleg, Finally the issue was nothing to do with the async client. Now we are experimenting with connection and response timeouts, setting just 1ms for both. In the blocking client, we get connection and response timeouts for all requests we send. But with the async client we are not able

Re: Help with async client

On Thu, 2016-03-17 at 17:51 +0100, Joan Balagueró wrote: > Hello, > > I hope this is the last question ... On our proxy we are reading the response > from the backend with a FutureCallback. On the complete method, > we process the response body in this way: > > public void

Re: Help with async client

; > > We have a test app that sends xml requests to our proxy. If the response is > not found in cache, the proxy uses the http client to get the responses > from the back end. > > > > Starting 20 threads, with the blocking client we reach about 700 requests > per

Help with async client

, the proxy uses the http client to get the responses from the back end. Starting 20 threads, with the blocking client we reach about 700 requests per second. With the async client, the pattern we are seeing is: 20 requests are processed, then a 5 second pause, then 20 more requests processed

Re: Async client

> Here we have 2 questions: > > 1. Hasn't the async client a retry handler and a stale check validation? Presently HttpAsyncClient does not support automatic request re-execution. Stale connection check is only relevant for classic (blocking) i/o. You can safely ignore it. > >

Async client

Hello, We are starting to work with the Async http client. We are creating a PoolingNHttpClientConnectionManager (translating our old PoolingHttpClientConnectionManager to a PoolingNHttpClientConnectionManager). Here we have 2 questions: 1. Hasn't the async client a retry handler and a stale

Re: Osgi and the TCCL and the async client

Oleg, let me start with a more coherent explanation, and that might lead to an idea about what sort of PR would be tasteful. The Async http client is an example of a thing that creates threads, accepts objects, and calls those objects from those threads. Meanwhile, there are things in the world

Re: Osgi and the TCCL and the async client

On Sat, 2016-01-02 at 19:35 -0500, Benson Margulies wrote: > It would be convenient if there was some way to tell the HTTP client > what class loader to use as the Thread Context Classloader when > calling the FutureCallback. Otherwise, it's prone (in OSGi) to be for > the the http component OSGI

Re: Problem with Async client

On Tue, 2014-08-12 at 16:57 -0700, Alex Oscherov wrote: I periodically (approximately in 0.5% of the cases) experience problem working with async client connecting to IIS 7.5. The problem manifests itself in callback never returning (neither completed, failed or canceled methods get called

Re: Problem with Async client

with async client connecting to IIS 7.5. The problem manifests itself in callback never returning (neither completed, failed or canceled methods get called). I've got some logging from one of such failures. It always ends with org.apache.http.impl.conn.ConnectionShutdownException. Any recommendations

Re: Problem with Async client

with async client connecting to IIS 7.5. The problem manifests itself in callback never returning (neither completed, failed or canceled methods get called). I've got some logging from one of such failures. It always ends with org.apache.http.impl.conn.ConnectionShutdownException. Any

Problem with Async client

I periodically (approximately in 0.5% of the cases) experience problem working with async client connecting to IIS 7.5. The problem manifests itself in callback never returning (neither completed, failed or canceled methods get called). I've got some logging from one of such failures. It always

Re: Pending requests not cancelled when async client is closed (http async client 4.0.1)

On Wed, 2014-03-05 at 14:57 +0200, Jose Dillet wrote: I have observed some differences between httpasyncclient 4.0-beta3 and 4.0.1 when the client is closed / shutdown and there are still pending requests. This can be observed by running AsyncClientHttpExchange and closing the client while

Pending requests not cancelled when async client is closed (http async client 4.0.1)

I have observed some differences between httpasyncclient 4.0-beta3 and 4.0.1 when the client is closed / shutdown and there are still pending requests. This can be observed by running AsyncClientHttpExchange and closing the client while the request is not yet completed. a)

Re: Http async client doesn't handle large requests

On Fri, 2014-01-03 at 15:04 -0800, Alex Oscherov wrote: I have a problem making http async client working with Exchange server through IIS 7.5. It looks very similar to HTTPASYNC-51 but now it has nothing to do with authentication. When I send relatively small request everything works fine

Re: HTTP async client and accessing server certificate (SSL)

On Thu, 2013-05-30 at 15:07 -0400, Sachin Nikumbh wrote: Hi Oleg, Thanks for your reply. I started digging through the Apache async client code and have come with a way to access the server certificate immediately after the SSL handshake in the verify method of SSLSetupHandler, To achieve

Re: HTTP async client and accessing server certificate (SSL)

digging through the Apache async client code and have come with a way to access the server certificate immediately after the SSL handshake in the verify method of SSLSetupHandler, To achieve this, I created my own MySSLLayeringStrategy class that extends SSLLayeringStrategy as shows below

Re: HTTP async client and accessing server certificate (SSL)

Hi Oleg, Thanks for your reply. I started digging through the Apache async client code and have come with a way to access the server certificate immediately after the SSL handshake in the verify method of SSLSetupHandler, To achieve this, I created my own MySSLLayeringStrategy class that extends

Re: HTTP async client and accessing server certificate (SSL)

On Mon, 2013-05-13 at 22:10 -0400, Sachin Nikumbh wrote: Hi Oleg, Thanks a lot for the response. I have one more question. In my client application, I need to provide extra authorization based on the common name in the server certificate. I want to allow the request-response exchange (I

Re: HTTP async client and accessing server certificate (SSL)

, Oleg Kalnichevski ol...@apache.org wrote: On Mon, 2013-04-29 at 11:27 -0400, Sachin Nikumbh wrote: Hi, I am currently using the HTTP async client in my application to communicate with a proprietary server. Now, I need to extend the functionality to include HTTPS support. We need

Re: HTTP async client and accessing server certificate (SSL)

On Mon, 2013-04-29 at 11:27 -0400, Sachin Nikumbh wrote: Hi, I am currently using the HTTP async client in my application to communicate with a proprietary server. Now, I need to extend the functionality to include HTTPS support. We need to provide client authentication and I have

HTTP async client and accessing server certificate (SSL)

Hi, I am currently using the HTTP async client in my application to communicate with a proprietary server. Now, I need to extend the functionality to include HTTPS support. We need to provide client authentication and I have the following picture of how I can provide client credentials. My first

Re: Suggested parameters for highly parallel async client

On Fri, 2013-02-08 at 15:23 -0800, vigna wrote: Just to complete the discussion, I finally set up the async client properly and it's pulling around 5000p/s, whereas the blocking client (with 1000 threads) has peaks of 1-15000 p/s, and average around 8000p/s, which is in line with your

Re: Suggested parameters for highly parallel async client

://httpcomponents.10934.n7.nabble.com/Suggested-parameters-for-highly-parallel-async-client-tp18644p19269.html Sent from the HttpClient-User mailing list archive at Nabble.com. - To unsubscribe, e-mail: httpclient-users-unsubscr

Re: Suggested parameters for highly parallel async client

On Fri, 2013-02-08 at 18:26 -0500, Jean-Marc Spaggiari wrote: From my personal experience a decent blocking HTTP client can be expected to outperform a decent non-blocking HTTP client by 50 to 100%, but such a massive difference does look very suspicious. My guess, though, that the way

Re: Suggested parameters for highly parallel async client

-for-highly-parallel-async-client-tp18644p19271.html Sent from the HttpClient-User mailing list archive at Nabble.com. - To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h

Re: Suggested parameters for highly parallel async client

On Sat, 2013-02-09 at 08:24 -0800, vigna wrote: Oleg Kalnichevski wrote I am working on improving HttpAsyncClient performance right now and I expect it to get better, but overall with a relatively small number of concurrent connections (1000) I expect HttpClient to outperform it by

Re: Suggested parameters for highly parallel async client

Just to complete the discussion, I finally set up the async client properly and it's pulling around 5000p/s, whereas the blocking client (with 1000 threads) has peaks of 1-15000 p/s, and average around 8000p/s, which is in line with your predictions. -- View this message in context: http

Re: Suggested parameters for highly parallel async client

From my personal experience a decent blocking HTTP client can be expected to outperform a decent non-blocking HTTP client by 50 to 100%, but such a massive difference does look very suspicious. My guess, though, that the way pages are being processed can be a limiting factor more more than

Suggested parameters for highly parallel async client

threads pushing 4000 async requests into a default DefaultHttpAsyncClient) we see completely different behaviours. The sync client fetches more than 1 pages/s, the async client speed fetches 50 p/s. Should we increase the number of threads or the I/O interval of the IOReactor? Or are we doing

Re: HTTP Async client and SO_SNDBUF

that org.apache.commons.httpclient.params.HttpConnectionParams* *class exposes it. I am comparing the throughput of the HTTP async client with Sun's HttpURLConnection. The test case is a single threaded application that's sending ~1Mb of data around 1000 number of times. With Wireshark, I see that apache HTTP client's request content-length

Re: HTTP Async client and SO_SNDBUF

, I found that org.apache.commons.httpclient.params.HttpConnectionParams* *class exposes it. I am comparing the throughput of the HTTP async client with Sun's HttpURLConnection. The test case is a single threaded application that's sending ~1Mb of data around 1000 number of times

Re: HTTP Async client and SO_SNDBUF

on this topic, I found that org.apache.commons.httpclient.params.HttpConnectionParams* *class exposes it. I am comparing the throughput of the HTTP async client with Sun's HttpURLConnection. The test case is a single threaded application that's sending ~1Mb of data around 1000 number

HTTP Async client and SO_SNDBUF

of the HTTP async client with Sun's HttpURLConnection. The test case is a single threaded application that's sending ~1Mb of data around 1000 number of times. With Wireshark, I see that apache HTTP client's request content-length never exceeds 4096 bytes whereas HttpURLConnectioncan have content-length

Re: Multiple HTTP async client instances and java.nio.channels.AsynchronousCloseException

On Thu, 2012-11-15 at 16:42 -0500, Sachin Nikumbh wrote: Hi, I have successfully used the HTTP Async client. It's working great for the most part. In my application I am creating multiple instances of DefaultHttpAsyncClient. However, I get java.nio.channels.AsynchronousCloseException once

Re: Multiple HTTP async client instances and java.nio.channels.AsynchronousCloseException

Hi Oleg, Thanks for your response. On Fri, Nov 16, 2012 at 10:59 AM, Oleg Kalnichevski ol...@apache.orgwrote: On Thu, 2012-11-15 at 16:42 -0500, Sachin Nikumbh wrote: Hi, I have successfully used the HTTP Async client. It's working great for the most part. In my application I am

Re: Multiple HTTP async client instances and java.nio.channels.AsynchronousCloseException

On Fri, 2012-11-16 at 11:44 -0500, Sachin Nikumbh wrote: Hi Oleg, Thanks for your response. On Fri, Nov 16, 2012 at 10:59 AM, Oleg Kalnichevski ol...@apache.orgwrote: On Thu, 2012-11-15 at 16:42 -0500, Sachin Nikumbh wrote: Hi, I have successfully used the HTTP Async client

Http Async Client: Connection already open

Hi, Occasionally I'll get this error when executing a call but would like to understand the actual source of the problem and if there is some configuration I can change to prevent it from happening again. java.lang.IllegalStateException: Connection already open at

Re: Http Async Client: Connection already open

On Mon, 2012-11-12 at 11:08 -0500, Mark Greene wrote: Hi, Occasionally I'll get this error when executing a call but would like to understand the actual source of the problem and if there is some configuration I can change to prevent it from happening again.

Re: HTTP Async client and HTTP response 413

On Mon, 2012-11-12 at 12:10 -0500, Sachin Nikumbh wrote: Hi, I am trying out the HTTP async client and have some sporadic behavior when it comes to HTTP response 413. The server I am communicating with has a request size limit. When my request content exceeds this limit, the server sends

Re: Http Async Client: Connection already open

Sure no problem, JIRA is here: https://issues.apache.org/jira/browse/HTTPASYNC-30 On Mon, Nov 12, 2012 at 11:40 AM, Oleg Kalnichevski ol...@apache.orgwrote: On Mon, 2012-11-12 at 11:08 -0500, Mark Greene wrote: Hi, Occasionally I'll get this error when executing a call but would like to

Re: HTTP Async Client and maximum connections per address

Hi, I don't think there is any limitation on HTTP async client side. Server side, only few of your requests will be replied at the same time based on the server configuration and all your other requests will just timed out. But client side, you can do almost what ever you want. JM 2012/11/8

Re: HTTP Async Client and maximum connections per address

On Thu, 2012-11-08 at 22:54 -0500, Sachin Nikumbh wrote: Hi, I am trying the HTTP async client and trying to figure out how to get/set the maximum number of connections per address. What is the default that's being used? The HTTP specification recommends 2 number of connections per address

HTTP Async Client - Address already in use with

I'm running into an issue where after making about 20k requests to a single host (200 concurrently) I start seeing these exceptions' java.net.BindException: Address already in use at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:532)

Re: HTTP Async Client - Address already in use with

On 2 November 2012 19:58, Mark Greene mgre...@hubspot.com wrote: I'm running into an issue where after making about 20k requests to a single host (200 concurrently) I start seeing these exceptions' java.net.BindException: Address already in use at sun.nio.ch.Net.connect(Native Method) at

HTTP Async Client Digest Authentication over HTTP 1.0 style connection

Hi, I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example http://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/examples/org/apache/http/examples/nio/client

Re: HTTP Async Client Digest Authentication over HTTP 1.0 style connection

On Thu, 2012-01-12 at 08:29 -0800, pwang wrote: Hi, I'm trying to use the HTTP Async client v4.0 alpha 3 to communicate with a HTTP v1.0-style server with Basic Digest authentication. I started with the basic example http://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient