Feedback
Did this article resolve your question/issue?

   

Article

java.net.SocketException: Too many open files on starting many AppServers

« Go Back

Information

 
Titlejava.net.SocketException: Too many open files on starting many AppServers
URL NameP23706
Article Number000140197
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: UNIX
Question/Problem Description
Getting error trying to start the nth AppServer or WebSpeed Broker

"ulimit -a" and "ulimit -Ha" both shows "open files" as 1024
Steps to Reproduce
Clarifying Information
Error MessageServerSocketsIPC <operation> IOException : <IOException_string> : <IOExceptionMsg_string> (8127)

java.net.SocketException: Too many open files : Too many open files (8127)
Defect/Enhancement Number
Cause
The process exceeds limit on file descriptors. There should be supporting information in the OS log files.
Resolution
Add "ulimit -n 100000" into the proadsv script, just before jvmstart.
Then restart AdminServer and all broker processes.

If ulimit -Hn is bigger than ulimit -n, increase ulimit "ulimit -n xxx".
If ulimit -n reaches ulimit -Hn setting, adjust kernel.

Refer to the 'man' pages for specific information.
Workaround
Notes
References to Other Documentation:

Progress Article(s):
000015355, "AppServer shuts down with error 8046"
Last Modified Date12/29/2017 8:49 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.