Oleksiy Stashok-2 wrote:
>
> On 08/23/2011 04:00 PM, Gili wrote:
>> Gili wrote:
>>> Does anyone have any idea on what's going on? 500ms seems extremely slow
>>> for something as simple as URL redirects, especially when all
>>> communication is taking place on localhost.
>>>
>> I tracked it down to this stack-trace:
>>
>> SocketInputStream.read() invoked by
>> BufferedInputStream.fill() invoked by
>> BufferedInputStream.read1() invoked by
>> BufferedInputStream.read() invoked by
>> HttpClient.parseHTTPHeader() invoked by
>> HttpURLConnection.getInputStream() invoked by
>> HttpURLConnection.getResponseCode() invoked by
>> URLConnectionClientHandler._invoke()
>>
>> Still no idea why this is happening...
> Looks like at this step client tries to read more data from the server,
> so may be it's not really a client problem.
> What are you using on the server side?
>
> You may also try to capture the network traffic/stats to check where the
> actual delay appears.
>
> WBR,
> Alexey.
>
Right. Both the client and server seem to hint the other is at fault. Is
there a tool I can run in the middle that will prove once and for all when
each request / response actually gets sent?
Thanks,
Gili
--
View this message in context: http://jersey.576304.n2.nabble.com/Slow-redirects-using-HttpUrlConnection-tp6712832p6717335.html
Sent from the Jersey mailing list archive at Nabble.com.