Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Unexpected delay after each HTTP response

cowwoc wrote:
> 
> Hi,
> 
> I'm running Jetty 7.4.4.v20110707. Every time I place an HTTP request
> (using an application I wrote, not a web browser) I am getting a 500 ms
> delay between the time the servlet returns the response and the time the
> client begins receiving any bytes. I spent a lot of time trying to figure
> out whether the problem was in the client or server. In the end, I ended
> up using Fidler HTTP proxy between the two and got the following:
> 
> ClientConnected: 16:34:40.486
> ClientBeginRequest: 16:34:40.486
> ClientDoneRequest: 16:34:40.486
> Determine Gateway: 0ms
> DNS Lookup: 0ms
> TCP/IP Connect: 0ms
> HTTPS Handshake: 0ms
> ServerConnected: 16:34:40.486
> FiddlerBeginRequest: 16:34:40.486
> ServerGotRequest: 16:34:40.486
> ServerBeginResponse: 16:34:40.986
> ServerDoneResponse: 16:34:40.986
> ClientBeginResponse: 16:34:40.986
> ClientDoneResponse: 16:34:40.986
> 
>         Overall Elapsed: 00:00:00.5000500
> 
> I also had debug logs in a Filter and it reported:
> 
> 2011-08-23 16:34:40.487,TRACE,ConnectionFilter.doFilter,qtp8806446-17
> start HTTP/1.1 GET http://10.0.1.32/devices
> 2011-08-23 16:34:40.489,TRACE,ConnectionFilter.doFilter,qtp8806446-17 end
> HTTP/1.1 GET http://10.0.1.32/devices
> 
> Notice how, from ConnectionFilter's point of view, the request ends at
> 40.489 but from Fiddler's point of view, the response begins at 40.986.
> ConnectionFilter is the outer-most Filter running on my server so I assume
> any delays past this point are coming from Jetty. I assume I have
> something misconfigured. Any idea what it could be?
> 
> Thanks,
> Gili
> 

On a related note, I'm unable to enable logging to slf4j to track down this
problem.

1. I'm launching Jetty from Maven using:

      <plugin>
        <groupId>org.mortbay.jetty</groupId>
        <artifactId>jetty-maven-plugin</artifactId>
        <version>7.4.4.v20110707</version>
        <configuration>
          <scanIntervalSeconds>5</scanIntervalSeconds>
          <connectors>
            <connector
implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
              <port>80</port>
            </connector>
          </connectors>        
        </configuration>
      </plugin>

2. I've added slf4j to the project POM
3. I've set logging level to TRACE
4. Jetty never logs to slf4j.
5. If I add -Dorg.eclipse.jetty.util.log.DEBUG=true to MAVEN_OPTS, Jetty
seem to log to stderr instead of slf4j.

Any ideas?

Thanks,
Gili

--
View this message in context: http://jetty.1047016.n5.nabble.com/Unexpected-delay-after-each-HTTP-response-tp4728842p4730459.html
Sent from the jetty-users mailing list archive at Nabble.com.


Back to the top