The number of open file descriptors in use by tomcat exceed maximum [on hold]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We have a web application written in java (using Java-EE on server side and GWT for client side).
We use nginx on CentOS as Web Server and two tomcat on CentOS as application servers. All of these servers are virtual machine. also using hazelcast as shared storage of application servers.
But after about 12 hours the number of open file descriptors in use by tomcat exceed maximum, also number of threads exceed to 8000. So we had to restart tomcat each 12 hours!
How many threads or opened file descriptors is normal for about 500 concurrent online user?
How can I find the wrong config or wrong code or concurrency bug and solve this problem? any Idea?
EDIT
I run lsof -p 7314 > output.txt command (7314 is tomcat pid) and check output file. The Number of file descriptors with FD, TYPE and NAME fields is like below.
FD No
********************
cwd: 1
rtd: 1
txt: 2
mem: 146
#[r|u|w] 3904 (like 456r, 234u, 123w)
TYPE No
********************
DIR: 2
REG: 199
CHR: 8
IPv6: 1039
unix: 4
FIFO: 1868
a_inode: 934
NAME No
*************************
eventpoll: 934
[node] -> [node]: 1034 (node is the name of computer node)
pipe: 1868
system-path: 209
socket: 8
tomcat lsof concurrency
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, roaima, JigglyNaga 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
0
down vote
favorite
We have a web application written in java (using Java-EE on server side and GWT for client side).
We use nginx on CentOS as Web Server and two tomcat on CentOS as application servers. All of these servers are virtual machine. also using hazelcast as shared storage of application servers.
But after about 12 hours the number of open file descriptors in use by tomcat exceed maximum, also number of threads exceed to 8000. So we had to restart tomcat each 12 hours!
How many threads or opened file descriptors is normal for about 500 concurrent online user?
How can I find the wrong config or wrong code or concurrency bug and solve this problem? any Idea?
EDIT
I run lsof -p 7314 > output.txt command (7314 is tomcat pid) and check output file. The Number of file descriptors with FD, TYPE and NAME fields is like below.
FD No
********************
cwd: 1
rtd: 1
txt: 2
mem: 146
#[r|u|w] 3904 (like 456r, 234u, 123w)
TYPE No
********************
DIR: 2
REG: 199
CHR: 8
IPv6: 1039
unix: 4
FIFO: 1868
a_inode: 934
NAME No
*************************
eventpoll: 934
[node] -> [node]: 1034 (node is the name of computer node)
pipe: 1868
system-path: 209
socket: 8
tomcat lsof concurrency
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, roaima, JigglyNaga 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have a web application written in java (using Java-EE on server side and GWT for client side).
We use nginx on CentOS as Web Server and two tomcat on CentOS as application servers. All of these servers are virtual machine. also using hazelcast as shared storage of application servers.
But after about 12 hours the number of open file descriptors in use by tomcat exceed maximum, also number of threads exceed to 8000. So we had to restart tomcat each 12 hours!
How many threads or opened file descriptors is normal for about 500 concurrent online user?
How can I find the wrong config or wrong code or concurrency bug and solve this problem? any Idea?
EDIT
I run lsof -p 7314 > output.txt command (7314 is tomcat pid) and check output file. The Number of file descriptors with FD, TYPE and NAME fields is like below.
FD No
********************
cwd: 1
rtd: 1
txt: 2
mem: 146
#[r|u|w] 3904 (like 456r, 234u, 123w)
TYPE No
********************
DIR: 2
REG: 199
CHR: 8
IPv6: 1039
unix: 4
FIFO: 1868
a_inode: 934
NAME No
*************************
eventpoll: 934
[node] -> [node]: 1034 (node is the name of computer node)
pipe: 1868
system-path: 209
socket: 8
tomcat lsof concurrency
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We have a web application written in java (using Java-EE on server side and GWT for client side).
We use nginx on CentOS as Web Server and two tomcat on CentOS as application servers. All of these servers are virtual machine. also using hazelcast as shared storage of application servers.
But after about 12 hours the number of open file descriptors in use by tomcat exceed maximum, also number of threads exceed to 8000. So we had to restart tomcat each 12 hours!
How many threads or opened file descriptors is normal for about 500 concurrent online user?
How can I find the wrong config or wrong code or concurrency bug and solve this problem? any Idea?
EDIT
I run lsof -p 7314 > output.txt command (7314 is tomcat pid) and check output file. The Number of file descriptors with FD, TYPE and NAME fields is like below.
FD No
********************
cwd: 1
rtd: 1
txt: 2
mem: 146
#[r|u|w] 3904 (like 456r, 234u, 123w)
TYPE No
********************
DIR: 2
REG: 199
CHR: 8
IPv6: 1039
unix: 4
FIFO: 1868
a_inode: 934
NAME No
*************************
eventpoll: 934
[node] -> [node]: 1034 (node is the name of computer node)
pipe: 1868
system-path: 209
socket: 8
tomcat lsof concurrency
tomcat lsof concurrency
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Ahmad
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Ahmad
1
asked 10 hours ago
Ahmad
1
1
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, roaima, JigglyNaga 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, roaima, JigglyNaga 1 hour ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago
add a comment |Â
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a debugging issue. Ask your developers to investigate and fix.
– roaima
2 hours ago