Re: [jetty-users] Help trying to investigate a file descriptor leak

Le Mon, 26 Feb 2018 10:10:45 -0500, Brian Reichert a écrit : > On Mon, Feb 26, 2018 at 10:08:41AM +0100, m...@ow2.org wrote: > > Hi Jan, > > > > Le Tue, 20 Feb 2018 16:25:04 +1100, > > Jan Bartel a ??crit : > > > > > We haven't had any reports of file descriptor leaks that I'm > > > aware

Re: [jetty-users] Help trying to investigate a file descriptor leak

On Mon, Feb 26, 2018 at 10:08:41AM +0100, m...@ow2.org wrote: > Hi Jan, > > Le Tue, 20 Feb 2018 16:25:04 +1100, > Jan Bartel a ??crit : > > > We haven't had any reports of file descriptor leaks that I'm aware of. > > Thank you very much for spending time to answer. > > > >

Re: [jetty-users] Help trying to investigate a file descriptor leak

Hi Jan, Le Tue, 20 Feb 2018 16:25:04 +1100, Jan Bartel a écrit : > We haven't had any reports of file descriptor leaks that I'm aware of. Thank you very much for spending time to answer. > > How are you serving static content with Jetty - are you using a > ResourceHandler,

Re: [jetty-users] Help trying to investigate a file descriptor leak

We haven't had any reports of file descriptor leaks that I'm aware of. How are you serving static content with Jetty - are you using a ResourceHandler, or are you using the DefaultServlet, or something else? If you are using the DefaultServlet, check how it is configured - do you have caching

[jetty-users] Help trying to investigate a file descriptor leak

Hello everybody. I need a guess if the issue below could come from Jetty. We run a webapp (XWiki) at https://www.ow2.org The application is reached through Apache as a reverse proxy. Jetty is 9.4.6.v20170531 running on Debian (9.3) JVM is 8u151-b12-1~deb9u1 The issue I observe from the xwiki