Re: No Response to TCP RESET (???)

2015-05-14 Thread Mark Johnson
After upgrading to HttpAysnClient 4.1 and HttpClient 4.4.1 and testing for the last 3 days, I have not been able to reproduce this anymore. Thanks for pushing me in that direction. Thanks, Mark On 5/12/2015 7:07 AM, Oleg Kalnichevski wrote: On Tue, 2015-05-12 at 07:03 -0500, Mark Johnson wr

Re: No Response to TCP RESET (???)

2015-05-12 Thread Mark Johnson
I have not done a thread dump but have a trace and wireshark capture. However I'm trying to reproduce this using the 4.1 async client. I'll post some files when I complete that. On 5/12/2015 7:41 AM, Stefan Magnus Landrø wrote: You say the app hangs - do you know where it hangs? do you have

Re: No Response to TCP RESET (???)

2015-05-12 Thread Stefan Magnus Landrø
You say the app hangs - do you know where it hangs? do you have a thread dump you could provide? (use jstack or jcmd) 2015-05-10 17:10 GMT+02:00 Mark Johnson : > What happens at this point is we have tried to issue an HTTP GET (but > nothing goes out on the wire) and there's no timeout or excepti

Re: No Response to TCP RESET (???)

2015-05-12 Thread Oleg Kalnichevski
On Tue, 2015-05-12 at 07:03 -0500, Mark Johnson wrote: > I thought I did upgrade to 4.1. Does it still appear as 4.0.1? > Looks to me that way 2015-05-11 16:59:06,356 | DEBUG | I/O dispatcher 8 | headers | 96 - com.servicemesh.io - 1.0.0.0 | http-outgoing-29 >> GET /api/versions HTTP/1.1 2015-0

Re: No Response to TCP RESET (???)

2015-05-12 Thread Mark Johnson
I thought I did upgrade to 4.1. Does it still appear as 4.0.1? On 5/12/2015 2:31 AM, Oleg Kalnichevski wrote: On Mon, 2015-05-11 at 17:10 -0500, Mark Johnson wrote: Here is the trace messages from the HTTPClient library and a wireshark capture. As I said earlier, this doesn't happen all the

Re: No Response to TCP RESET (???)

2015-05-12 Thread Oleg Kalnichevski
On Mon, 2015-05-11 at 17:10 -0500, Mark Johnson wrote: > Here is the trace messages from the HTTPClient library and a wireshark > capture. As I said earlier, this doesn't happen all the time. > > Thanks. > > https://www.dropbox.com/s/j2548hgx5x1biml/trace.log?dl=0 > > https://www.dropbox.com/s

Re: No Response to TCP RESET (???)

2015-05-11 Thread Stefan Magnus Landrø
I'll try to have a look at the tcpdump tomorrow. Stefan Sendt fra min iPhone > Den 12. mai 2015 kl. 00.10 skrev Mark Johnson : > > Here is the trace messages from the HTTPClient library and a wireshark > capture. As I said earlier, this doesn't happen all the time. > > Thanks. > > https://

Re: No Response to TCP RESET (???)

2015-05-11 Thread Mark Johnson
Here is the trace messages from the HTTPClient library and a wireshark capture. As I said earlier, this doesn't happen all the time. Thanks. https://www.dropbox.com/s/j2548hgx5x1biml/trace.log?dl=0 https://www.dropbox.com/s/i0wxlc5rvhvx73v/tcp-reset.pcapng?dl=0 On 5/11/2015 2:44 AM, Oleg Ka

Re: No Response to TCP RESET (???)

2015-05-11 Thread Oleg Kalnichevski
On Sun, 2015-05-10 at 10:10 -0500, Mark Johnson wrote: > What happens at this point is we have tried to issue an HTTP GET (but > nothing goes out on the wire) and there's no timeout or exception > thrown. So my client application hangs. > > I cannot see any evidence of that in the log. Pleas

Re: No Response to TCP RESET (???)

2015-05-10 Thread Mark Johnson
What happens at this point is we have tried to issue an HTTP GET (but nothing goes out on the wire) and there's no timeout or exception thrown. So my client application hangs. On 5/10/2015 6:51 AM, Oleg Kalnichevski wrote: On Fri, 2015-05-08 at 09:28 -0500, Mark Johnson wrote: Hi, I’'m ha

Re: No Response to TCP RESET (???)

2015-05-10 Thread Oleg Kalnichevski
On Fri, 2015-05-08 at 09:28 -0500, Mark Johnson wrote: > Hi, > > I’'m having intermittent hangs with a client application that uses the > async HTTPClient. (It’s an HTTPS connection also.) I'’ve turned on the > diagnostics logs (attached) and performed a wire capture. My guess is > that the server

No Response to TCP RESET (???)

2015-05-08 Thread Mark Johnson
Hi,I’'m having intermittent hangs with a client application that uses the async HTTPClient. (It’s an HTTPS connection also.) I'’ve turned on the diagnostics logs (attached) and performed a wire capture. My guess is that the server is not responding to a TCP RESET. One other variable - I'm going thr