Community
Participate
Working Groups
Build Identifier: We're seeing the issue when jetty client is pausing ( not sure exactly where) before reading a next chunk from the response. The response is sent as gzip from the server. If you can help in telling which class ( from jetty projects) to put a breakpoint ( where it collects the response), I can debug & can write a junit test case to publish it here. Reproducible: Always
Hi, Firstly, can you specify exactly which jetty version you're using? Have you tried doing a thread dump during the pause? Please post the output of that here. thanks Jan
Created attachment 199409 [details] thread dump We're using jettty-client-7.3.1v20110307. Please find attached thred dump
Thanks for the thread dump.Do you have 2 HttpClients? It is usually best to have only 1 HttpClient, as each has multiple threads and is capable of connecting to multiple destinations. Nothing unusual in the dump. I suggest you: 1. send a full description of the "pause". Does the response ever complete or not? How long is the "pause"? Is it consistent? 2. turn on debug logging: java -Dorg.eclipse.jetty.util.log.stderr.DEBUG=true -jar start.jar Look for output before and during the "pause". Particularly for output like: JVM BUG(s) - injecting delay JVM BUG(s) - cancelled keys JVM BUG(s) - recreating selector 3. do several repeated thread dumps during the pause to see what, if anything has changed 4. obtain a tcpdump/wireshark trace and see what is happening during the "pause" 5. try running on a non-windows box and see if the behaviour is the same 6. try a more recent version of the jvm to see if the behaviour is the same 7. try upgrading to jetty-7.4.4 and see if the behaviour is the same
Could be related to bug #355948 which I just filed.
One more question. What version of Java are you using?
hrishi_sir, Do you have any of the info we requested so we can progress this? thanks Jan
Due to lack of information, I am closing this issue. If the problem is not addressed by the information in issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=355948, please reopen and supply the information we previously requested so we can investigate.