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: SocketException: Too many open files

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
coming out of our Java code whenever we try to open a URL:


java.net.SocketException: Too many open files
at java.net.Socket.createImpl(Socket.java:331)
at java.net.Socket.connect(Socket.java:450)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(DashoA12275)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(DashoA12275)
at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(DashoA122
75)
at sun.net.www.protocol.https.HttpsClient.doConnect(DashoA12275)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
at sun.net.www.protocol.https.HttpsClient.(DashoA12275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA12275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA12275)
at sun.net.www.protocol.https.HttpsClient.a(DashoA12275)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.plainConne
ct(DashoA12275)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Da
shoA12275)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(DashoA12275)



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 we're just pounding this harder than it will ever get
hit in the real world?  I'm also seeing this as well:





SEVERE: Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=80]
ignored exception: java.net.SocketException: Too many open files
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(Defau
ltServerSocketFactory.java:107)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.
java:356)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:52
9)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:619)
at java.lang.Thread.run(Thread.java:534)
Feb 1, 2005 4:53:08 PM org.apache.tomcat.util.net.PoolTcpEndpoint
closeServerSocket
SEVERE: Caught exception trying to unlock accept.
java.net.SocketException: Too many open files
at java.net.Socket.createImpl(Socket.java:331)
at java.net.Socket.(Socket.java:304)
at java.net.Socket.(Socket.java:124)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndp
oint.java:326)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.
java:397)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:52
9)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:619)
at java.lang.Thread.run(Thread.java:534)
Feb 1, 2005 4:53:08 PM org.apache.tomcat.util.net.PoolTcpEndpoint
acceptSocket
WARNING: Reinitializing ServerSocket


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 we're just pounding this harder than it will ever get
: hit in the real world?

I don't recall which OS you run, but look into tuning the TCP stack for
the short, bursty connection style of HTTP.  There's a setting that
determines how long your server hangs onto a socket after the connection
has closed. 

For the life of me, I can't remember this parm right now, but I've seen
it here and there.  

Search the archives for "Too many open files" and my e-mail address.
You should turn up a post in which I've answered this question before.

-QM


-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SocketException: Too many open files

2005-02-01 Thread Stephen Charles Huey 
Do other Tomcat users often need to raise this limit on Linux?  In
addition to talking to website users, our Tomcat also has to talk to
another web server elsewhere on the internet to verify a lot of stuff...


- Original message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Users List" 
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 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
> coming out of our Java code whenever we try to open a URL:
> 
> java.net.SocketException: Too many open files

If you're on Linux, use ulimit -a to see what the limits are, and
ulimit -n to change the value. However, only root is allowed to get
more than 1024 files (does somebody knows why ?).


-- 
x
Rémy Maucherat
Developer & Consultant
JBoss Group (Europe) SàRL
x

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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
> coming out of our Java code whenever we try to open a URL:
> 
> java.net.SocketException: Too many open files

If you're on Linux, use ulimit -a to see what the limits are, and
ulimit -n to change the value. However, only root is allowed to get
more than 1024 files (does somebody knows why ?).


-- 
x
Rémy Maucherat
Developer & Consultant
JBoss Group (Europe) SàRL
x

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 application which is supposed to connect 
to a C++ client appliction through sockets. But it doesn't establish!!

From the logs (catalina.out) I got :
==
[...]
Jan 12, 2005 5:27:58 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: 
attributeAdded('D57CF5B49544DEE007778BB3F78EB407', 'cart', 
'[EMAIL PROTECTED]')
processRequest submit = : login
java.net.SocketException: Broken pipe
processRequest submit = : login
processRequest submit = : login
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh
CheckWebClient execute
checkWebClientConnexion -- 1105547298096
1990>2
java.net.SocketException: Broken pipe
processRequest submit = : refresh
processRequest submit = : refresh
java.net.SocketException: Broken pipe
processRequest submit = : refresh

[...]
==
I have no enough knowlegde but Tomcat and java to solve this problem. 
If some one can help me .

Cheers,
Cédric

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 call tracer (Unix) or TDImon (Windows), monitor until you got the
>> error, and then look through the logfile to see which system call was
>> giving you the error back.  That might give you some insight into what
>> your system is doing when this occurs...
>
> I'm on a Solaris system. So I take it you mean something like truss or 
> truss
> itself? I think I tried that once and gave up for some reason - I'll have 
> to go
> back to my notes to see why, I could've just run out of time.
>

You could probably find more details in the archives, but the message is due 
to a problem with the Socket implementation on Solaris (soTimeout I think, 
but I'm not sure, and too lazy to search myself :).  The short answer is 
that the message is pretty harmless, since TC catches it and continues 
processing.

> Do you know why this error might occur? I think the thing I'm really 
> looking for
> is to see if there's something I need to do on the server end, or if it's 
> a
> client problem. And I never see the error on my test server, just on the
> production one that has a greater load - the error doesn't SEEM to hurt
> anything, but then again catalina.out classifies it as SEVERE, so maybe 
> there's
> something to it that I'm missing!
>
> Thanks for your help!
> -- 
> Lynn Hollerman. 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 through the logfile to see which system call was
giving you the error back.  That might give you some insight into what
your system is doing when this occurs...
I'm on a Solaris system. So I take it you mean something like truss or truss
itself? I think I tried that once and gave up for some reason - I'll have to go
back to my notes to see why, I could've just run out of time.
Do you know why this error might occur? I think the thing I'm really looking for
is to see if there's something I need to do on the server end, or if it's a
client problem. And I never see the error on my test server, just on the
production one that has a greater load - the error doesn't SEEM to hurt
anything, but then again catalina.out classifies it as SEVERE, so maybe there's
something to it that I'm missing!
Thanks for your help!
--
Lynn Hollerman.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 connection'. You will see a 
'Configure' button. Click configure and you will see the properties for the nic 
card. Choose
the advanced tab. The NIC's in true server systems (like SuperMicro, Dell, HP, 
etc)
will allow you to set the Transmit and Recieve size (or 'descriptors' in some 
case).
By default this is set to 256. Set it to 1024.
If your NIC card does not have this property listed, contact the manufacturer 
about
where these settings are in the registry (and they ARE in the registry).

2. Change the TCP-IP parameters for the window size.
Open the registry.
Navigate to, or create: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add/Edit these keys:
- GlobalMaxTcpWindowSize, DWORD, 131400 (decimal)
- TcpWindowSize, DWORD, 131400 (decimal)
- Tcp1323Opts, DWORD, 3
You can use load testing to find the best values for these reg keys.

After changing the above, our throughput on the same hardware went up
by a factor of 4, and we stopped getting SocketExceptions, and other odd
socket-related errors we could never reproduce.

Check here for a good doc on the registry settings:
http://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm

Hope it helps,
Al G


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 throughput
5 to 7 times.)

Al G

- Original Message -
From: Hollerman Geralyn M <[EMAIL PROTECTED]>
Date: Friday, November 12, 2004 8:28 am
Subject: SocketException

> As I have mentioned in the past, I am still getting this error in 
> my catalina.out:
> 
> Nov 12, 2004 5:03:19 AM org.apache.tomcat.util.net.TcpWorkerThread 
> runItSEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid 
> argument
> This is the complete text of the error - no stack trace, nothing 
> more.I am using 
> Tomcat 5.0.16 and this is the error I get; I got a similar error 
> using 4.1.24. 
> The error isn't constant, and I don't know how to reproduce it. I 
> don't think it 
> has anything to do with the number of open files or memory; I have 
> looked into 
> the possibility that the error might be due to either of those 
> (after reading 
> some comments I found after searching on Google and the archives 
> of this list) 
> and I think I've eliminated those possibilities. Does anyone have 
> any idea what 
> might cause this error?
> 
> Thanks!
> 
> -- 
> Lynn Hollerman.
> 
> ---
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 until you got the
error, and then look through the logfile to see which system call was
giving you the error back.  That might give you some insight into what
your system is doing when this occurs...

- Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 database; JDK 
1.4.2_05 is used on this Solaris 5.8 system. Apache (2.0.50) is used in 
a sort of uncommon way: all it does is redirect requests (using 
mod_rewrite), as there are at least 2 domain names that can be used to 
get to the same place - Tomcat is ultimately all that is used.

Since the application I'm running is for students and the fall semester 
has recently begun, the load has increased significantly in the past few 
weeks. I have a development system, and I never see this error on there; 
I have only seen it on our production system, in the past few weeks, 
under the higher load. I *suspect* that the error is caused by some user 
action, as in pressing the "Back" button or repeatedly clicking 
somewhere - my suspicion is based on the fact that several of us in my 
building have tried to produce this error but are unable to, but then 
again, we know what to expect, what to do, and what not to do when it 
comes to this application!
Some more info on this - I was looking around my logs files, and found that I 
also saw this message in Tomcat 4.1.24, but there was a different, longer error 
message:

java.net.SocketException: Invalid argument
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:240)
at java.net.Socket.setTcpNoDelay(Socket.java:771)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.java:468)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:564)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)

although, it appears that at the time this error message was generated, Tomcat 
was throwing an OutofMemory error - I'm not sure if one had anything to do with 
the other, but judging from the date on the log, that was an error we were 
getting often at that time...

Hope this helps!
--
Lynn Hollerman.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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 PROTECTED]
>Subject: SocketException while writing to Outputstream
>
>Hi all,
>
>I am running Tomcat 4.1.27 on JDK 1.4.2, Win2k.
>I am getting a SocketException (Software caused connection abort) while
>writing to Outputstream. Searched the net but couldn't find an useful
>answer. What could be the issue?
>Any hint would be greatly appreciated
>
>Given below is the stack trace.
>
> java.net.SocketException: Software caused connection abort: socket
write
>error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at
>org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.
doWr
>i
>te(InternalOutputBuffer.java:668)
> at
>org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOut
putF
>i
>lter.java:166)
> at
>org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf
fer.
>j
>ava:523)
> at org.apache.coyote.Response.doWrite(Response.java:524)
> at
>org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java
:384
>)
> at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439)
> at org.apache.coyote.tomcat4.OutputBuffer.flush(OutputBuffer.java:345)
> at
>org.apache.coyote.tomcat4.CoyoteResponse.flushBuffer(CoyoteResponse.jav
a:55
>5
>)
> at
>org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(CoyoteRespon
seFa
>c
>ade.java:227)
> at
>javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper
.jav
>a
>:189)
> at
>org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDis
patc
>h
>er.java:446)
> at
>org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispa
tche
>r
>.java:356)
> at
>com.onmobile.sc.servlets.OnmServiceInvoker.forwardToService(OnmServiceI
nvok
>e
>r.java:242)
> at
>com.onmobile.sc.servlets.OnmServiceInvoker.doGet(OnmServiceInvoker.java
:155
>)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
>org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
>n
>FilterChain.java:247)
> at
>org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
>h
>ain.java:193)
> at
>com.onmobile.sc.accesslayer.OnmAccessBroker.handleInvokerRequest(OnmAcc
essB
>r
>oker.java:277)
> at
>com.onmobile.sc.accesslayer.OnmAccessBroker.doFilter(OnmAccessBroker.ja
va:1
>2
>1)
> at
>org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
>n
>FilterChain.java:213)
> at
>org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
>h
>ain.java:193)
> at
>org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal
ve.j
>a
>va:256)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:643)
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
> at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
>org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal
ve.j
>a
>va:191)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:643)
> at
>org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.j
ava:
>2
>46)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:641)
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
> at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
>org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24
16)
> at
>org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav
a:18
>0
>)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:643)
> at
>org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV
alve
>.
>java:171)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:641)
> at
>org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav
a:17
>2
>)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
>k
>eNext(StandardPipeline.java:641)
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
> at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
>org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve
.jav
>a
>:174)
> at
>org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo

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 page.
http://projects.accessibilityforum.org/tomcat-docs/jk2/jk2/configwebcom.html

But it worked so I guess that is good.

Frank

- Original Message - 
From: "Frank Febbraro" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Thursday, January 08, 2004 10:43 AM
Subject: SocketException - JK2, Tomcat 4.1.29, IIS 5.1


> When accessing pages on my Tomcat server via IIS and isapi_redirector2.dll
I
> get the following errors on every page request.
>
> The errors below are for a simple page invokation like
> http://localhost/asis/index.jsp
>
> Each page is returned successfully, but there are reams of errors
generated.
>
> Thanks for any help. I have included the catalina.out, isapi.log,
> jk2.properties and workers2.properties file.
>
> Thanks again,
> Frank
>
> In the TOMCAT LOG I get:
>
> SEVERE: Error, processing connection
> java.net.SocketException: Software caused connection abort: recv failed
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
> at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:548)
> at
> org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:486)
> at
>
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:603)
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
> a:666)
> at java.lang.Thread.run(Thread.java:536)
> StandardContext[/asis]:  Mapped to servlet 'default' with servlet path
> '/includes/style.css' and path info 'null' and update=true
> Jan 8, 2004 10:23:06 AM org.apache.jk.common.ChannelSocket
processConnection
> SEVERE: Error, processing connection
> java.net.SocketException: Software caused connection abort: recv failed
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
> at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:548)
> at
> org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:486)
> at
>
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:603)
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
> a:666)
> at java.lang.Thread.run(Thread.java:536)
>
> In the ISAPI LOG I get:
> [Thu Jan 08 10:23:06 2004] (error ) [jk_worker_ajp13.c (341)]
> ajp13.service() error sending, reconnect channel.socket:localhost:8009 -1
0
> No error
> [Thu Jan 08 10:23:06 2004] (error ) [jk_service_iis.c (157)]
> jk_ws_service_t::head, ServerSupportFunction failed
> [Thu Jan 08 10:23:06 2004] (error ) [jk_handler_response.c (178)]
> handler.response() Error sending response[Thu Jan 08 10:23:06 2004]
(error )
> [jk_worker_ajp13.c (416)]  ajp13.service() ajpGetReply recoverable error 3
> [Thu Jan 08 10:23:06 2004] (error ) [jk_service_iis.c (157)]
> jk_ws_service_t::head, ServerSupportFunction failed
> [Thu Jan 08 10:23:06 2004] (error ) [jk_handler_response.c (178)]
> handler.response() Error sending response[Thu Jan 08 10:23:06 2004]
(error )
> [jk_worker_ajp13.c (416)]  ajp13.service() ajpGetReply recoverable error 3
> [Thu Jan 08 10:23:06 2004] (error ) [jk_worker_ajp13.c (512)]
> ajp13.service() Error  forwarding ajp13:localhost:8009 1 0
>
> My jk2.properties file:
>
> # Handler configuration
> #
> handler.list=request,container,channelSocket
>
> # Socket configuration
> #
> channelSocket.port=8009
> channelSocket.address=127.0.0.1
> channelSocket.maxPort=port+10
>
>
> My workers2.properties file:
> # shared memory
> #
> [shm]
> file=D:/tomcat-4.1.29/work/shm.file
> size=1048576
>
> # alternate logging to keep mod_jk2 logging separate from IIS logging
> #
> [logger.file:0]
> file=D:/tomcat-4.1.29/logs/jk2.log
> [workerEnv:]
> info=Global server options
> timing=1
> debug=0
> logger=logger.file:0
>
> # IP socket channel
> #
> [channel.socket:localhost:8009]
> port=8009
> host=127.0.0.1
>
> # define the ajp13 worker
> #
> [ajp13:localhost:8009]
> channel=channel.so

Re: SocketException

2002-12-03 Thread maninder s batth 
netstat -a -p should do it , if you are from unix world.download nmap 
for windows . that will give you process and port information
just use keywords nmap for windows in google and ull get it

Ram Kochhar wrote:

Hi,
 I just installed the tomcat and have not done anything except to try to
run start.bat.  My operating system is
windows 98.  How do I found out about the port or another process.  I also
installed microsoft network
protocal  so that TCP/IP is installed but it did not help.  Tomcat version
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 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 tomcat 4.1 and I get the following SocketException
 

error
 

when I try to start the server.  I will
appreciate any help.  I have a stand alone machine with no modem or
 

network
 

card with jdk1.4.Thanks


Ram Kochhar

[EMAIL PROTECTED]

D:\Tomcat 4.1\bin>catalina.bat run
Using CATALINA_BASE:   d:\tomcat~1.1
Using CATALINA_HOME:   d:\tomcat~1.1
Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
Using JAVA_HOME:   d:\jdk1.4
Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.SocketException: Socket type not supported: create
  at java.net.ServerSocket.createImpl(ServerSocket.java:244)
  at java.net.ServerSocket.getImpl(ServerSocket.java:202)
  at java.net.ServerSocket.bind(ServerSocket.java:308)
  at java.net.ServerSocket.bind(ServerSocket.java:266)
  at java.net.ServerSocket.(ServerSocket.java:182)
  at java.net.ServerSocket.(ServerSocket.java:138)
  at
org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
faultServerSocketFactory.java:96)
  at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
nt.java:263)
  at
org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)

  at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
java:1002)
  at
org.apache.catalina.core.StandardService.initialize(StandardService.j
ava:579)
  at
org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
a:2244)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
  at
 

org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
 

  at
 

org.apache.catalina.startup.Catalina.process(Catalina.java:180)
 

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)

Catalina.start: LifecycleException:  Protocol handler initialization
 

failed:
 

jav
a.net.SocketException: Socket type not supported: create
LifecycleException:  Protocol handler initialization failed:
java.net.SocketExce
ption: Socket type not supported: create
  at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
java:1004)
  at
org.apache.catalina.core.StandardService.initialize(StandardService.j
ava:579)
  at
org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
a:2244)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
  at
 

org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
 

  at
 

org.apache.catalina.startup.Catalina.process(Catalina.java:180)
 

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.stop: LifecycleException:  This server has not yet been started
LifecycleException:  This server has not yet been started
  at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
  at
 

org.apache.catalina.startup.Catalina.exe

Re: SocketException

2002-12-03 Thread Ram Kochhar 
Hi,
  I just installed the tomcat and have not done anything except to try to
run start.bat.  My operating system is
 windows 98.  How do I found out about the port or another process.  I also
installed microsoft network
 protocal  so that TCP/IP is installed but it did not help.  Tomcat version
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 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 tomcat 4.1 and I get the following SocketException
error
> >when I try to start the server.  I will
> >appreciate any help.  I have a stand alone machine with no modem or
network
> >card with jdk1.4.Thanks
> >
> >
> >Ram Kochhar
> >
> >[EMAIL PROTECTED]
> >
> > D:\Tomcat 4.1\bin>catalina.bat run
> >Using CATALINA_BASE:   d:\tomcat~1.1
> >Using CATALINA_HOME:   d:\tomcat~1.1
> >Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
> >Using JAVA_HOME:   d:\jdk1.4
> >Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
> >INFO: Loading registry information
> >Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
> >INFO: Creating new Registry instance
> >Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
> >INFO: Creating MBeanServer
> >Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
> >SEVERE: Error initializing endpoint
> >java.net.SocketException: Socket type not supported: create
> >at java.net.ServerSocket.createImpl(ServerSocket.java:244)
> >at java.net.ServerSocket.getImpl(ServerSocket.java:202)
> >at java.net.ServerSocket.bind(ServerSocket.java:308)
> >at java.net.ServerSocket.bind(ServerSocket.java:266)
> >at java.net.ServerSocket.(ServerSocket.java:182)
> >at java.net.ServerSocket.(ServerSocket.java:138)
> >at
> >org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
> >faultServerSocketFactory.java:96)
> >at
> >org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
> >nt.java:263)
> >at
> >org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
> >
> >at
> >org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
> >java:1002)
> >at
> >org.apache.catalina.core.StandardService.initialize(StandardService.j
> >ava:579)
> >at
> >org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
> >a:2244)
> >at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> >at
org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
> >at
org.apache.catalina.startup.Catalina.process(Catalina.java:180)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >java:39)
> >at
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >sorImpl.java:25)
> >at java.lang.reflect.Method.invoke(Method.java:324)
> >at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
> >
> >Catalina.start: LifecycleException:  Protocol handler initialization
failed:
> >jav
> >a.net.SocketException: Socket type not supported: create
> >LifecycleException:  Protocol handler initialization failed:
> >java.net.SocketExce
> >ption: Socket type not supported: create
> >at
> >org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
> >java:1004)
> >at
> >org.apache.catalina.core.StandardService.initialize(StandardService.j
> >ava:579)
> >at
> >org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
> >a:2244)
> >at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> >at
org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
> >at
org.apache.catalina.startup.Catalina.process(Catalina.java:180)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >java:

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 tomcat 4.1 and I get the following SocketException error
>when I try to start the server.  I will
>appreciate any help.  I have a stand alone machine with no modem or network
>card with jdk1.4.Thanks
>
>
>Ram Kochhar
>
>[EMAIL PROTECTED]
>
> D:\Tomcat 4.1\bin>catalina.bat run
>Using CATALINA_BASE:   d:\tomcat~1.1
>Using CATALINA_HOME:   d:\tomcat~1.1
>Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
>Using JAVA_HOME:   d:\jdk1.4
>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
>INFO: Loading registry information
>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
>INFO: Creating new Registry instance
>Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
>INFO: Creating MBeanServer
>Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
>SEVERE: Error initializing endpoint
>java.net.SocketException: Socket type not supported: create
>at java.net.ServerSocket.createImpl(ServerSocket.java:244)
>at java.net.ServerSocket.getImpl(ServerSocket.java:202)
>at java.net.ServerSocket.bind(ServerSocket.java:308)
>at java.net.ServerSocket.bind(ServerSocket.java:266)
>at java.net.ServerSocket.(ServerSocket.java:182)
>at java.net.ServerSocket.(ServerSocket.java:138)
>at
>org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
>faultServerSocketFactory.java:96)
>at
>org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
>nt.java:263)
>at
>org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
>
>at
>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>java:1002)
>at
>org.apache.catalina.core.StandardService.initialize(StandardService.j
>ava:579)
>at
>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>a:2244)
>at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
>at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
>at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>java:39)
>at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>sorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:324)
>at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>
>Catalina.start: LifecycleException:  Protocol handler initialization failed:
>jav
>a.net.SocketException: Socket type not supported: create
>LifecycleException:  Protocol handler initialization failed:
>java.net.SocketExce
>ption: Socket type not supported: create
>at
>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>java:1004)
>at
>org.apache.catalina.core.StandardService.initialize(StandardService.j
>ava:579)
>at
>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>a:2244)
>at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
>at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
>at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>java:39)
>at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>sorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:324)
>at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>Catalina.stop: LifecycleException:  This server has not yet been started
>LifecycleException:  This server has not yet been started
>at
>org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
>)
>at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
>at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
>at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>java:39)
>at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>sorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:324)
>at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>
>
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 


--
To unsubscribe, e-mail:

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 servlet o that tomcat doesn't understand the 
connection.

Hola Enrique Cea. El 27/05/01 a la(s) 2:22 wrote:

>I think hat the exception occurs before init method of the servlet.
>
>The code of the java program that connect to the server is:
>
> Code of the client --
>
>URL servlet = new
>URL("http://127.0.0.1:8080/prueba/anyadirMensajeServlet";);
>
>Mensaje msg = new MensajeReal();
>
>URLConnection con = servlet.openConnection();
>con.setDoInput(true);
>con.setDoOutput(true);
>con.setUseCaches(false);
>con.setRequestProperty("Content-Type",
>"application/x-www-form-urlencoded");
>ObjectOutputStream out = new ObjectOutputStream(con.getOutputStream());
>out.writeObject(msg);
>out.writeInt(1);
>
>out.flush();
>out.close();
,

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 J. Ortega


> -Mensaje original-
> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 27 de marzo de 2001 14:04
> Para: [EMAIL PROTECTED]
> Asunto: SocketException with Tomcat 3.2.1
> 
> 
> Dear all,
> 
> We are using Tomcat 3.2.1 with Microsoft IIS4 and IE5. After 
> upgrading from
> Tomcat version 3.1 to version 3.2.1, we are receiving the 
> SocketException
> and messages described below. We are trying to import a 
> JavaScript-file,
> generated by Tomcat (via JSP), in an HTML-file. Each time a
> JavaScript-function is called, the SocketException occurs. 
> Does anyone know
> what the problem is here? Is this a Tomcat-bug or are we 
> doing something
> wrong? Any help would be appreciated!!!
> 
> This is what we are trying:
> 
>  HTML <-- JS-file (import) <-- |via Tomcat 3.2| <-- JSP-file
> 
> This is what we are getting:
> 
> SocketException:
> 
> 2001-03-27 01:54:19 - ContextManager: SocketException reading request,
> ignored - java.net.SocketException: Connection reset by peer: 
> JVM_recv in
> socket input stream read
>  at java.net.SocketInputStream.socketRead(Native Method)
>  at java.net.SocketInputStream.read(SocketInputStream.java:86)
>  at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
>  at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
>  at
> org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpR
> equestAdapter.java:115)
>  at
> org.apache.tomcat.core.BufferedServletInputStream.doRead(Buffe
> redServletInputStream.java:106)
>  at
> org.apache.tomcat.core.BufferedServletInputStream.read(Buffere
> dServletInputStream.java:128)
>  at
> javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
>  at
> org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequ
> est(HttpRequestAdapter.java:129)
>  at
> org.apache.tomcat.service.http.HttpConnectionHandler.processCo
> nnection(HttpConnectionHandler.java:195)
>  at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoin
> t.java:416)
>  at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPo
> ol.java:498)
>  at java.lang.Thread.run(Thread.java:484)
> 
> Other problems:
> ---
> 2001-03-27 01:54:19 - Ctx( /op0010 ): 404 R( /op0010 + 
> /imap/map/none +
> null) null
> 2001-03-27 01:54:09 - Ctx(  ): 400 R( /) null
> 
> The SocketException appears only once or twice after 
> restarting Tomcat. The
> other two problems appear each time the JavaScript-function 
> is triggered in
> the webpage (which is in an onMouseOver-event, thus about 20 
> times each
> second!!!)
> 
> Regards,
> 
> Joeri
> 
>