Craig, Roger C [ITS] writes: > We are running Linux under VM on a mainframe. We keep running into this > "Too many open files" problem with one of our WebLogic Servers: > Sep 8, 2003 5:58:25 AM CDT> <Notice> <WebLogicServer> <000203> > <Reopening listen socket on port 7201> > <Sep 8, 2003 5:59:30 AM CDT> <Critical> <WebLogicServer> <000204> > <Failed to listen on port 7201, failure count: 79, failing for > 1,063,013,260 seconds, java.net.SocketException: Too many open files> > <Sep 8, 2003 5:59:30 AM CDT> <Critical> <WebLogicServer> <000206> > <Attempting to close and reopen the server socket on port 7201> > > We end up having to bounce the server (or Linux image) when we get this > condition. Has anyone experienced this? Also is there a good way to > display the number of open files?
It's just an administrative limit these days (either via /etc/security/limits.conf for session initiated via PAM using pam_limits or via a default of, usually, 1024). Raise the limit in whichever way you like: WebLogic may have a preferred way of doing this depending on how its username starts up a session or you can use limits.conf (if WebLogic goes via a PAM config that includes pam_limits) or else use ulimit (bash) or limit (tcsh) in your daemon startup script. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
