RE: SocketException: Too many open files

2005-02-02 Thread Randall Svancara
You need to increase the maximum number of open file descriptors for your platform. There are lots of documents on how to do this. Thanks, Randall -Original Message- From: Stephen Charles Huey [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 4:30 PM To: Tomcat User Subject:

Re: SocketException: Too many open files

2005-02-01 Thread Remy Maucherat
On Tue, 01 Feb 2005 17:29:51 -0600, Stephen Charles Huey [EMAIL PROTECTED] wrote: I'm running some simple but fast-pounding test programs against our Tomcat server from a machine on the same network, and we've been tuning our database, etc, based on this. But right now, I'm seeing a new one

Re: SocketException: Too many open files

2005-02-01 Thread Stephen Charles Huey
List tomcat-user@jakarta.apache.org Date: Wed, 2 Feb 2005 00:52:56 +0100 Subject: Re: SocketException: Too many open files On Tue, 01 Feb 2005 17:29:51 -0600, Stephen Charles Huey [EMAIL PROTECTED] wrote: I'm running some simple but fast-pounding test programs against our Tomcat server from

Re: SocketException: Too many open files

2005-02-01 Thread QM
On Tue, Feb 01, 2005 at 05:29:51PM -0600, Stephen Charles Huey wrote: : java.net.SocketException: Too many open files : [snip] : We're opening lots of these, and it appears we're opening more than a : maximum number of connections to the internet. Is there a way to bump : this up? Or maybe

Re: SocketException: Broken pipe

2005-01-13 Thread Cédric Buschini
Hi again Sorry to insist but it 's quiet important. I running out of ideas to solve my problem.. :'( Is there a way to allow/denied access using sockets Cédric Hi there, I got a problem with a Tomcat 5.5.6 server and Java (jdk and jre 1.5.0_01) on a Debian R3. On my server, there is a JAVA

Re: SocketException

2004-11-13 Thread Bill Barker
Hollerman Geralyn M [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Peter Crowther wrote: SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid argument Hmm. An EINVAL from the socket layer. Are you running UNIX or Windows? Depending on which, I'd get hold of a system

RE: SocketException

2004-11-12 Thread Peter Crowther
From: Hollerman Geralyn M [mailto:[EMAIL PROTECTED] SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid argument Hmm. An EINVAL from the socket layer. Are you running UNIX or Windows? Depending on which, I'd get hold of a system call tracer (Unix) or TDImon (Windows), monitor

Re: SocketException

2004-11-12 Thread agidden
This will happen on the Windows platform when using network interface cards which are improperly configured (which is the default for many NIC's). If you are on Windows, and using HTTP/HTTPS for your system reply back and I can send you the info on how to resolve this (and increase your TCP-IP

RE: SocketException

2004-11-12 Thread agidden
Ok then. If you take the time to measure the throughput on a good Windows 2000 server you may find that on a good day you are only getting about 2Mbps. By default, many of the network drivers are setup this way, but you can do something about it. 1. Open the properties of your 'local area

RE: SocketException

2004-11-12 Thread Hollerman Geralyn M
Peter Crowther wrote: SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid argument Hmm. An EINVAL from the socket layer. Are you running UNIX or Windows? Depending on which, I'd get hold of a system call tracer (Unix) or TDImon (Windows), monitor until you got the error, and then look

Re: SocketException

2004-09-01 Thread Hollerman Geralyn M
Hollerman Geralyn M wrote: I am getting this error in catalina.out: Sep 1, 2004 12:41:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid argument (this is the entire message) I am running Tomcat 5.0.16, going against a MySQL 4.0.17

RE: SocketException while writing to Outputstream

2004-07-27 Thread Shapira, Yoav
Hi, The user closed the browser while you were generating your page. Get a later version of tomcat where this has been fixed. Yoav Shapira Millennium Research Informatics -Original Message- From: Sreejith [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 27, 2004 8:38 AM To: [EMAIL

Re: SocketException - JK2, Tomcat 4.1.29, IIS 5.1

2004-01-08 Thread Frank Febbraro
In worker2.properties I changed the following and the errors disappeared: I added keepalive=0 (supposedly the default) to the channel.socket so it now looks like this # IP socket channel # [channel.socket:localhost:8009] port=8009 host=127.0.0.1 keepalive=0 There is no field description on this

Re: SocketException

2002-12-03 Thread Ram Kochhar
4.1.9. Thanks. Ram Kochhar - Original Message - From: Paul Campbell [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, December 02, 2002 10:32 PM Subject: Re: SocketException I have jdk1.4 and tomcat 4.1 and it runs with out a problem. Did you make some changes

Re: SocketException

2002-12-03 Thread maninder s batth
PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, December 02, 2002 10:32 PM Subject: Re: SocketException I have jdk1.4 and tomcat 4.1 and it runs with out a problem. Did you make some changes to a config file? Did you invoke some servlet, of jsp that led to the exception

Re: SocketException

2002-12-02 Thread Paul Campbell
I have jdk1.4 and tomcat 4.1 and it runs with out a problem. Did you make some changes to a config file? Did you invoke some servlet, of jsp that led to the exception? Is there another process that might be using the same port? At 08:46 PM 12/2/02 -0800, you wrote: Hi, I have installed

Re: SocketException

2001-05-27 Thread Enrique Cea
Now I'm sure that the exception comes before the init method of the servlet. Also I have tried to connect to ser servlet using IExplorer and get an This URL doesn't support GET method but the servlet do the init method, so I'm thinking that there is problem with the way I connect to the

RE: SocketException with Tomcat 3.2.1

2001-03-27 Thread Ignacio J. Ortega
I known problem...well better to say it's a known non problem.. IE closes sockets on HTTP/1.0 connections when see the last-modified header... It's solved on 3.3 ( next Milestone will caught it ) and in 4.0 as it has a complete HTTP/1.1 implementation for standalone use... Saludos , Ignacio