On Thu, 2010-07-22 at 13:20 -0400, Brooks, Kenneth S wrote:
> Oleg,
> 
> Another team in my company is using Axis2 1.5.1 (with HttpClient 3.1) as 
> clients of a webservice.
> 
> They are seeing the following:
> 
> *       When communicating from source -> destination via http, everything 
> works fine.
> o       Responses come in less than 2 seconds and the FIN, FINACK happens 
> within 5 seconds. Almost no RST happening.

This probably means that the application is not re-using connections. Is
this intentional? 


> *       When communicating from source -> destination via https (no other 
> changes) they are seeing these symptoms:
> o       Over 90% of all calls never see the FINACK sent back by client. This 
> causes a very large number of RST to happen. The majority of the RST get 
> RSTACK back, but not all.
> o       About 1.4% of all calls get "Connect Timeout" errors because they 
> think that the socket is still in use.
> 
> That is the very high level that I can gather from them so far.
> 
> Basically what I'm asking you is
> 1) Have you seen any issues with httpclient (or axis use of httpclient) when 
> using https

Personally I have never experienced any issues with HTTPS using both HC
3.1 and HC 4.0. I have never really used Axis2, though. Never managed to
come to terms with it no matter how hard I tried. 

> 2) Is httpclient even in the mix when it comes to low level protocol 
> communication like the FIN and FINACK? Or are we barking up the wrong tree 
> and need to look at some OS/Hardware level area instead?
> 

Java applications in general have no means to controlling TCP/IP
networking on such a low level. What might well be the case, though,
that Java application does not explicitly close the socket on its end
thus leaving the connection is a half open state until the socket gets
garbage collected. I _believe_ Axis2 used to have issues with connection
management and used to be prone to leaking client-side HTTP connections.

Is there a reason connections are not being re-used? Maybe the problem
could be mitigated by reducing the number of connections that need to be
established in the first place?

I am not a TCP/IP specialist by any stretch of imagination so take it
for what it is worth to you.

Cheers

Oleg  



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to