Tomcat 6.0.32
Java 1.6.27
Apache 2.0
RedHat 6.x 64 bit
/proc/sys/fs/file-max = 3233344
We experienced an issue where we were getting the error too many open files
in tomcat. The server manager increase the amount of open files to the above.
But the error kept coming back even after rebooting
On Wed, Aug 24, 2011 at 17:21, Campbell, Lance la...@illinois.edu wrote:
Tomcat 6.0.32
Java 1.6.27
Apache 2.0
RedHat 6.x 64 bit
/proc/sys/fs/file-max = 3233344
We experienced an issue where we were getting the error too many open files
in tomcat. The server manager increase the amount of
10:24 AM
To: Tomcat Users List
Subject: Re: Too many open files error
On Wed, Aug 24, 2011 at 17:21, Campbell, Lance la...@illinois.edu wrote:
Tomcat 6.0.32
Java 1.6.27
Apache 2.0
RedHat 6.x 64 bit
/proc/sys/fs/file-max = 3233344
We experienced an issue where we were getting the error too
On Wed, Aug 24, 2011 at 17:33, Campbell, Lance la...@illinois.edu wrote:
The file /etc/security/limits.d is empty. What would be an example of
something you would expect to see in there that would relate to changing the
RMILIT_NFILE value?
It's a directory, not a file. Create a file named
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance,
On 8/24/2011 11:21 AM, Campbell, Lance wrote:
Tomcat 6.0.32 Java 1.6.27 Apache 2.0 RedHat 6.x 64 bit
/proc/sys/fs/file-max = 3233344
We experienced an issue where we were getting the error too many
open files in tomcat. The server
2007 9:43:00
Subject: Re: Too Many Open Files error
Thanks Jim,
It was previously set to 1024, and I quadrupled it. When you say ulimit
is persistent will it persist across a reboot?
I don't seem to have the command lsof, I'll try and apt-get it.
Cheers
Dan
Jim Cox wrote:
On 10/19/07
then place ulimit -n in the catalina startup scripts?
Setting a limit with ulimit is sticky (i.e. persistent), so there's
no need to stick it in the startup script.
However, you didn't answer the previous two questions about (1) how
many files did Tomcat have open when you got the Too many open
Hi Dan,
You can try sysctrl.conf file. Add in the ulimit -n for open files.
- Original Message
From: Daniel M Garland [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, 19 October 2007 9:43:00
Subject: Re: Too Many Open Files error
Thanks Jim
On 10/19/07, Daniel M Garland [EMAIL PROTECTED] wrote:
Thanks Jim,
It was previously set to 1024, and I quadrupled it. When you say ulimit
is persistent will it persist across a reboot?
I don't seem to have the command lsof, I'll try and apt-get it.
Cheers
Dan
The settings should
(1) how
many files did Tomcat have open when you got the Too many open files
error, and (2) what the current ulimit setting for open files is. If
you provide those answers people here can help you out a bit more.
-
To start a new
Should I then place ulimit -n in the catalina startup scripts?
Jim Cox wrote:
On 10/18/07, Daniel M Garland [EMAIL PROTECTED] wrote:
Hi all
I'm seeing a problem on a Tomcat instance:
18-Oct-2007 12:41:47 org.apache.tomcat.util.net.AprEndpoint$Acceptor run
SEVERE: Socket accept failed
Hi all
I'm seeing a problem on a Tomcat instance:
18-Oct-2007 12:41:47 org.apache.tomcat.util.net.AprEndpoint$Acceptor run
SEVERE: Socket accept failed
org.apache.tomcat.jni.Error: Too many open files
at org.apache.tomcat.jni.Socket.accept(Native Method)
at
Am Donnerstag 18 Oktober 2007 schrieb Daniel M Garland:
Hi all
I'm seeing a problem on a Tomcat instance:
18-Oct-2007 12:41:47 org.apache.tomcat.util.net.AprEndpoint$Acceptor run
SEVERE: Socket accept failed
org.apache.tomcat.jni.Error: Too many open files
at
On 10/18/07, Daniel M Garland [EMAIL PROTECTED] wrote:
Hi all
I'm seeing a problem on a Tomcat instance:
18-Oct-2007 12:41:47 org.apache.tomcat.util.net.AprEndpoint$Acceptor run
SEVERE: Socket accept failed
org.apache.tomcat.jni.Error: Too many open files
at
14 matches
Mail list logo
