Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] time out
With Amazon you have to be aware of the timeouts that Amazon's own network services also apply to your webapp.
This is outside of Jetty, and cannot be configured by Jetty.
Look into consoles at Amazon that you have, there will be a few timeouts parameters that you should adjust to suit your needs properly.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Tue, Sep 23, 2014 at 6:46 AM, Oscar Jorge Pérez Pérez <juliusvernis@xxxxxxxxx> wrote:
Thanks for both responses,

Linux I am using is from Amazon (Amazon Linux AMI release 2013), maybe is some default timeout value of those instances.


Best regards

Oscar J. Perez

2014-09-23 15:23 GMT+02:00 Michael Dykman <mdykman@xxxxxxxxx>:

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.

On 23 Sep 2014 09:06, "Jesse McConnell" <jesse.mcconnell@xxxxxxxxx> wrote:
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. :)

cheers,
Jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Tue, Sep 23, 2014 at 6:02 AM, Oscar Jorge Pérez Pérez
<juliusvernis@xxxxxxxxx> wrote:
> Hello,
>
> 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
> jetty-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Back to the top