groet,
Lawrence Lamprecht
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Wednesday, June 03, 2009 10:20 PM
To: Tomcat Users List
Subject: RE: java.net.SocketException: Too many open files
From: John Cartwright [mailto:john.c.cartwri...@noaa.gov
From: john.c.cartwri...@noaa.gov [mailto:john.c.cartwri...@noaa.gov]
Can someone please help to to understand what might cause such an
exception?
File descriptor exhaustion - the process has run out of fds. Any i/o could use
a file descriptor, whether that's socket to httpd, socket to
Here is the code
void acceptConnections() {
if( log.isDebugEnabled() )
log.debug(Accepting ajp connections on + port);
while( running ) {
try{
MsgContext ep=createMsgContext(packetSize);
ep.setSource(this);
Thanks for your suggestions Martin, I'll look into modifying the memory
parameters. Strange thing is that this has been running for weeks w/o
any changes in the configuration or contexts.
--john
Martin Gainty wrote:
Here is the code
void acceptConnections() {
if(
From: John Cartwright [mailto:john.c.cartwri...@noaa.gov]
Subject: Re: java.net.SocketException: Too many open files
I'll look into modifying the memory parameters.
That would be a complete waste of time. The heap size has nothing to do with
the problem you're seeing, and the discussion
Thanks for your reply Peter. Initially I was assuming that lsof was not
showing me files on disk that were being opened and read by servlets.
However, I've been unable to reproduce that in a more controlled setting.
Since this system has been running for weeks w/o any modification,
: Re: java.net.SocketException: Too many open files
To: users@tomcat.apache.org
Thanks for your suggestions Martin, I'll look into modifying the memory
parameters. Strange thing is that this has been running for weeks w/o
any changes in the configuration or contexts.
--john
Martin
