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