How do you enable HTTP/2 in your embedded application? Also, If you have configured your SslContextFactory, what does this configuration look like?
Lastly, what does your ThreadPool / Executor configuration look like? Joakim Erdfelt / [email protected] On Tue, Nov 20, 2018 at 9:01 AM Silvio Bierman <[email protected]> wrote: > Hello all, > > We are running Jetty 9.4.14 embedded in an application that runs on a > number of Ubuntu 18.10 servers. Last night we switched from HTTP1.1 only > to HTTP2. Today we are experiencing serious problems. Users can not > access the application or are experiencing extremely long latencies. At > the same time the server is almost idle. > We have configured the Ubuntu servers as almost default setups. > OpenJDK11 with Jetty using pure Java HTTPS. We have been doing this for > years now and each time we switched from HTTP1.1 to HTTP2 things started > falling apart. In the past we had reports of people not being able to > connect at all receiving spurious messages from their browsers (some of > which are undoubtedly outdated). We expected things to have improved by > now and decided to try again, with the above result. > > Are there additional things we need to take care of when using HTTP2 > when compared to HTTP1.1? More threads, different queue size, more file > handles etc? > > Any pointers would be very much appreciated. > > Kind regards, > > Silvio > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
