How to solve too many files issue?
This issue occur in two areas
1. If Web server, App server and Data base servers residing in One machine, then you m ayget this error
2. If socket timed out not mentioned then this issue may this issue.
Using ulimit -a command, we will find how many sockets had that machine. In any machine 1024 is the maximum sockets.
Bottleneck identification:
Using netstat -a|grep WAIT|wc -l command we will find how many sockets opened by the application. If 1024 connection are utilized then we will get too many open files.
If you want know which server opened more socket, just use lsof -p <Process ID> for finding the sockets opened by that process.
Internal Process of a socket: All HTTP requests internally used TCP connection. One TCP connection is one Socket in computer science language. So if you send n number of requests to the server , the server opens the socket to handle your requests but we need to close the sockets once your request got over other wise socket won't close, for this we need to mention the socket timed out.
Solutions:
For issue 1: Just increase the sockets using ulimit -Hn <Parameter> (Ex ulimit -Hn 2048)command, but it is not recommended , you have to discuss with your architect on this.
For issue 2: Just provide the socket time out in your server configuration file. In web server change the value in uri_worker.property file
This issue occur in two areas
1. If Web server, App server and Data base servers residing in One machine, then you m ayget this error
2. If socket timed out not mentioned then this issue may this issue.
Using ulimit -a command, we will find how many sockets had that machine. In any machine 1024 is the maximum sockets.
Bottleneck identification:
Using netstat -a|grep WAIT|wc -l command we will find how many sockets opened by the application. If 1024 connection are utilized then we will get too many open files.
If you want know which server opened more socket, just use lsof -p <Process ID> for finding the sockets opened by that process.
Internal Process of a socket: All HTTP requests internally used TCP connection. One TCP connection is one Socket in computer science language. So if you send n number of requests to the server , the server opens the socket to handle your requests but we need to close the sockets once your request got over other wise socket won't close, for this we need to mention the socket timed out.
Solutions:
For issue 1: Just increase the sockets using ulimit -Hn <Parameter> (Ex ulimit -Hn 2048)command, but it is not recommended , you have to discuss with your architect on this.
For issue 2: Just provide the socket time out in your server configuration file. In web server change the value in uri_worker.property file
