|Re: [jetty-users] time out|
Try hitting your application with curl or some other command line tool where you can control the client time out. I think that will indicate that Jetty is not the problem. It is likely a Chrome policy for remote servers.
I would recommend running a recent version, 9.2.3v20140905 being the
most recent. Asking for support related to a release candidate from a
year and a half ago is unlikely to garner much of a response. :)
On Tue, Sep 23, 2014 at 6:02 AM, Oscar Jorge Pérez Pérez
> I am using jetty-distribution-9.0.0.RC2 and I have a doubt regarding it.
> Configuration is almost default provided. Currently I deploy that
> distribution in Linux and Windows environment. Locally is Windows and is
> working fine (I am using Jersey 1.2).
> Problem is: In my local windows one request can take a longer time (for
> example more than 5 minutes) without any problem but when I use jetty
> deployed in linux machine, if that request takes more than 60 seconds,
> Chrome gets disconnected but request continues working in background.
> I have tried to use timeout and idletimeout in some places but I couldn't
> find where I should try to change timeout value.
> Note: during debug is same problem, if I place a breakpoint in code, calling
> remotely to linux server, after 60 seconds I can continue debugging but I
> see Chrome gets disconnected (circle indicating that is working finishes)
> Thanks in advance
> Oscar Perez
> jetty-users mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top