Re: [jetty-users] over 200K open files FIFO pipe

[Luke B <lukenbutters@xxxxxxxxx>]

Hi Simone,

This looks to be related to conscrypt.

You can go over to https://github.com/LukeButters/conscrypt-jetty

and run that to get up and running a jetter server with conscrypt which will have many many of those FIFO pipes left open.

(let me know if you need any help with it.)

At this stage I don't know if it is a bug in conscrypt or jetty.

-Luke

On Tue, Sep 10, 2019 at 12:56 AM Simone Bordet <sbordet@xxxxxxxxxxx> wrote:

Hi,

On Sun, Sep 8, 2019 at 10:09 AM Luke B <lukenbutters@xxxxxxxxx> wrote:
>
> Hi,
>
> I am running jetty server "9.4.19.v20190610".
> I have no .wars loaded and have made a bunch of http 1.0 requests to the jetty web server to a URL which does not exist resulting in a 404 from the jetty web server.
>
> What I noticed is that after some time the web server stopped responding, I was unable to run jmap to get a heap dump I instead got the message too many open files.
>
> Running lsof on the process gave me lines like:
> Service    5309 5347    root  515r     FIFO                0,9       0t0  172660316 pipe
> Service    5309 5347    root  516w     FIFO                0,9       0t0  172660316 pipe
> Service    5309 5347    root  517r     FIFO                0,9       0t0  172660317 pipe
> Service    5309 5347    root  518w     FIFO                0,9       0t0  172660317 pipe
> Service    5309 5347    root  519r     FIFO                0,9       0t0  172661057 pipe
> Service    5309 5347    root  520w     FIFO                0,9       0t0  172661057 pipe
>
>  cat openfiles.lsof.txt | grep 5309 | grep FIFO | wc
>  211947 2115471 18863283
>
> is that expected?

I tried this myself and cannot replicate, it's all good for me and no leaks.

If there are sockets leaked, I would rather expect "files" of type
IPv4, not FIFO, to show up.
I don't know what FIFO files are, but according to
https://stackoverflow.com/questions/15956452/troubleshooting-too-many-files-open-with-lsof
they are the streams of child processes?
In that case it's not Jetty (we don't spawn child processes).
According to https://linux.die.net/man/7/fifo, a FIFO file is a named
pipe, and again Jetty does not do that - I doubt the JVM does when
Jetty asks to use sockets.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users