Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Too Many Files
I'm guessing that most of these open files are going to be CLOSE_WAIT or TIME_WAIT, because if they are ESTABLISHED, then you just need a bigger machine :)

If they are waiting, then you need to work out why?  Bad clients? using http/1.0 from a proxy?  too long idle timeouts?  other settings?

I'm betting you are using nginx out front, it is using HTTP/1.0 to the server and you have a reasonably long timeout or a high request rate.  If that is the case get a front end that speaks a protocol version that is not decades old!  Or just use jetty direct!

If that's not the case, then more details are needed!

cheers
 



On 27 February 2016 at 00:41, Bill Ross <ross@xxxxxxxxxxxx> wrote:
Assuming you mean too many open files, do you really need that many open?

Sounds like you need to close something you are opening repeatedly.

Bill


On 2/26/16 3:00 PM, Mack Gerhardt wrote:

I have come across this in the past, where Too Many Files exception and jetty shutting down. I tweaked file server limits and it seemed to go away. But it seems like it is back.


I am running jetty jetty-9.2.13. I have bumped my file system max for the system and for the user running the jetty process. Any thoughts, I am running embedded jetty for websocket usage primarily. Any thoughts on best practices or how to avoid this error?


OS:

CentOS release 5.11 (Final)

Linux jetty12.6.18-404.el5



[root@jetty1 ~]# sysctl fs.file-max

fs.file-max = 5000000

[root@jetty1 ~]# sysctl fs.file-nr

fs.file-nr = 2550       0       5000000

[root@webproto10 ~]#

 

 

/etc/security/limits.conf


webadmin        hard    nofile          999999

webadmin        soft    nofile          999999

 

 

[root@jetty1 ~]# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 63817

max locked memory       (kbytes, -l) 32

max memory size         (kbytes, -m) unlimited

open files                      (-n) 999999

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 128312

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

 

 

webadmin@jetty1 : ~/paltalk/presence$ ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 63817

max locked memory       (kbytes, -l) 32

max memory size         (kbytes, -m) unlimited

open files                      (-n) 999999

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 128312

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

 

 



_______________________________________________
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