SocketException: Invalid argument

[Luis Torres]

Hello everyone,

I have a question regarding an error I'm seeing more every day in my 
catalina.out


11/10/2005 12:08:34 PM org.apache.tomcat.util.net.TcpWorkerThread runIt
GRAVE: Remote Host /10.49.156.64 SocketException: Invalid argument

It happens with diverse IP addresses, both inside our NAT and outside of 
it. The server is not behind a firewall and has a public IP address.


The setup is: Tomcat 4.131, default ports, JDK 1.5.0 update 2, Solaris 9

There's only one application on that server and it hasn't been modified 
in some weeks and looking in the web I found ppl with the same problem 
but so far no solutions.


Any ideas?

Luis

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

ssl SocketException: Software caused connection abort: recv failed

[Fco Javier Jiemnez]

Hello,

I have a problem with Tomcat 5.0.28 with SSL mode enabled + Struts 1.2 + 
Windows XP + j2sdk 1.4.2

When I use Tomcat in ssl mode i read this error in console every time that 
click a link aplication web.

10-may-2005 0:55:21 org.apache.tomcat.util.net.TcpWorkerThread runIt
GRAVE: Remote Host /192.168.0.1 SocketException: Software caused connection 
abort: recv failed


If  I use http in 8080, there isn't error but if I use https 8443 appears the 
error.

I uncomment server.xml to enable ssl mode in Tomcat(default port 8443) and y 
generate self-signed certificate with keytool (default password changeit)

Anybody helps me? What's the problem?


Thanks.

PD: Sorry but my english is bad ;P

RE: SocketException: Too many open files

[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

[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

[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

[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]

SocketException: Too many open files

[Stephen Charles Huey]

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(DashoA12275)
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.plainConnect(DashoA12275)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(DashoA12275)
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(DefaultServerSocketFactory.java:107)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:356)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529)
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(PoolTcpEndpoint.java:326)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:397)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529)
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]

Re: SocketException: Broken pipe

[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]

SocketException: Broken pipe

[Cédric Buschini]

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]

Re: SocketException

[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

[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

[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

[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

[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]

SocketException

[Hollerman Geralyn M]

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 runIt
SEVERE: 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]

SocketException: Software caused connection abort: recv failed

[Antony Paul]

Hi ,
I am getting this error when SSL is enabled.

Sep 10, 2004 11:14:30 AM org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Remote Host /192.168.4.66 SocketException: Software caused
connection abort: recv failed

This is on console. What may be the cause for it ?.

Tomcat 4.1.30
Java HotSpot(TM) Client VM - build 1.4.1_01-b01

I am using unsigned certificates.

rgds
Anto Paul

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

Re: SocketException

[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]

SocketException

[Hollerman Geralyn M]

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!

Has anyone seen this? Any ideas?
Thanks!
--
Lynn Hollerman.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

SocketException: Connection reset - Tomcat 5.0.27

[alan sparago]

When using Tomcat 5.0.27 the following error shows up in the catalina.log
file;
SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset
org.apache.tomcat.util.net.TcpWorkerThread runIt

The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and
checks periodically to make sure tomcat is running. It logs this error every
time it checks. When I switch to Tomcat 5.0.16 under the same exact
conditions this error does not show up in the log file.

Questions;
Is there a way to prevent this from being logged?
Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16?
If Tomcat cant be set up to not log this error, is there a way to log in as
INFO instead?

alan



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

SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset

[alan sparago]

When using Tomcat 5.0.27 the following error shows up in the catalina.log
file;

SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset

org.apache.tomcat.util.net.TcpWorkerThread runIt

 

The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and
checks every 5 secs to make sure tomcat is running (by checking the port
tomcat runs on). When I switch to Tomcat 5.0.16 under the same exact
conditions this does not show up in the log file.

 

It does not hurt the performance of Tomcat but it is causing a huge and
unreadable log file, and in addition, we monitor the log files for SEVERE
errors and send out an email when any occur 

 

Questions;

What exactly does this mean? (I believe it to mean a client closed the
connection to tomcat before tomcat had a chance to reply to it.)

Is there a way to prevent this from being logged?

Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16?

If Tomcat cant be set up to not log this error, is there a way to log in as
INFO instead?

 

RE: Urgent attention needed to solve mysterious SocketException error

[Ralph Einfeldt]

Are you running tomcat stand alone ?

One possible cause is that tomcat is trying to open a socket where 
nobody is listening. (Invalid argument or EINVAL is a common error
returned by all kind of socket operations in this case)

Without more of the stacktrace it's difficult (at least for me)
to say anything about the context where the problem is occuring.


> -Original Message-
> From: Adrian G. Klingel [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 05, 2004 5:27 PM
> To: [EMAIL PROTECTED]
> Subject: Urgent attention needed to solve mysterious SocketException
> error
> 
> 
> I'm running Tomcat 5.0.25 in our DMZ.  The server crashes 
> every day.  I see
> thousands and thousands of lines like this in Catalina.out:
>  
> Aug 5, 2004 10:50:31 AM 
> org.apache.tomcat.util.net.TcpWorkerThread runIt
> SEVERE: Remote Host /xx.xx.xx.1 SocketException: Invalid argument
>  
> That IP (obfuscated) is our gateway.  The application on this 
> server is not
> distributed, it does make some calls to an external database.
>  
> I can't find any documentation on this error.  I found one 
> reference to
> someone else who had the problem, but there were no solutions offered.
>  
> Any help is greatly appreciated.
>  
> Sincerely,
> Adrian
> 
>  
> 

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

Urgent attention needed to solve mysterious SocketException error

[Adrian G. Klingel]

I'm running Tomcat 5.0.25 in our DMZ.  The server crashes every day.  I see
thousands and thousands of lines like this in Catalina.out:
 
Aug 5, 2004 10:50:31 AM org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Remote Host /xx.xx.xx.1 SocketException: Invalid argument
 
That IP (obfuscated) is our gateway.  The application on this server is not
distributed, it does make some calls to an external database.
 
I can't find any documentation on this error.  I found one reference to
someone else who had the problem, but there were no solutions offered.
 
Any help is greatly appreciated.
 
Sincerely,
Adrian

 

RE: SocketException while writing to Outputstream

[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
&g

SocketException while writing to Outputstream

[Sreejith]

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.doWri
te(InternalOutputBuffer.java:668)
 at
org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFi
lter.java:166)
 at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.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.java:555
)
 at
org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(CoyoteResponseFac
ade.java:227)
 at
javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java
:189)
 at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch
er.java:446)
 at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher
.java:356)
 at
com.onmobile.sc.servlets.OnmServiceInvoker.forwardToService(OnmServiceInvoke
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(Application
FilterChain.java:247)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
 at
com.onmobile.sc.accesslayer.OnmAccessBroker.handleInvokerRequest(OnmAccessBr
oker.java:277)
 at
com.onmobile.sc.accesslayer.OnmAccessBroker.doFilter(OnmAccessBroker.java:12
1)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:213)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
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(StandardContextValve.ja
va:191)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2
46)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
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:2416)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:171)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
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.java
:174)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
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.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
 at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:392)
 at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
 at
org.apache.tomcat.util.threads.Threa

SocketException and NullPointerException

[Hollerman Geralyn M]

Folks,
I have 2 errors in my catalina.out that I'm trying to chase down, and for both 
I've about come up with zero in terms of figuring out what's causing them and/or 
how to "fix" them. I'd appreciate ANY ideas/suggestions/comments!

The first is of the form

Mar 22, 2004 8:38:32 AM org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Invalid argument
This one shows up somewhat sporadically - some days there will be several, other 
days, none.

The second looks like

StandardWrapperValve[uPortal]: Servlet.service() for servlet uPortal threw exception
java.lang.RuntimeException: java.lang.NullPointerException
java.lang.RuntimeException: java.lang.NullPointerException
at 
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3364)
at 
org.apache.xalan.transformer.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:427)
at 
org.jasig.portal.utils.SAX2FilterImpl.endDocument(SAX2FilterImpl.java:684)
at 
org.jasig.portal.utils.SAX2BufferImpl.outputBuffer(SAX2BufferImpl.java:210)
at org.jasig.portal.UserInstance.renderState(UserInstance.java:538)
at org.jasig.portal.UserInstance.writeContent(UserInstance.java:180)
at 
org.jasig.portal.PortalSessionManager.doGet(PortalSessionManager.java:246)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
[...] (I can give you the full trace, but it's long and ugly - I think you get 
the idea here)

Now, I know this one has something to do with the XML parser and probably the 
stylesheet used - something that's passed is null for some reason, and as far as 
the program is concerned, it shouldn't be. What could cause this? I get this 
error from our production system - I'm running the same version of Tomcat 
(5.0.16) on a development system as well, and the error never shows up there. I 
have the same versions of XML parsers on both boxes - the .class files in them 
that are used in the stack trace (like TransformerImpl) are the same on both 
systems (yes, I checked.). I'd really like to get this fixed - the server 
appears to start-up fine, with no errors listed.

Thanks for any feedback!!
--
Lynn Hollerman.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1.29 - IE SocketException - [ERROR] PoolTcpEndpoint - -Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]

[See Yam Lim]

Hi List,

I can only trigger this exception consistently under IE 6.0
browser. When using Mozilla 1.4 problem does not occur at all. It is on
FreeBSD 4.6 and I am using JDK 1.3.1.


[ERROR] PoolTcpEndpoint - -Endpoint
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] ignored
exception: java.net.SocketException: Software caused connection abort
java.net.SocketException: Software caused connection abort
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(Defau
ltServerSocketFactory.java:107)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.
java:371)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:55
3)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:666)
at java.lang.Thread.run(Thread.java:484)

[WARN] PoolTcpEndpoint - -Reinitializing ServerSocket

In order to debug the issue, the default server.xml with using port 8080
and CoyteConnectors is used. I have also looked into the Tomcat 4.1.29
codes which classes have to do with stacktrace above. 

As the log shows, the ServerSoket InetAddress is "addr=0.0.0.0/0.0.0.0".
Even it is reinitializing the Server Socket, it is still causing the
browser spinning, of course, another thread will be able accept. 
So is something to with Native Method on the FreeBSD? Or the
ThreadWithAttributes class somehow missing its attribute? Or is it
configuration issue? I actually didn't spend too much time on Tomcat
codes. Before I dig further on this issue and perform tcpdump. I am
asking if anyone of you experience the same problem. 

Any sort of information will be really helpful. Thanks in advance.

See Yam




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

Re: SocketException - JK2, Tomcat 4.1.29, IIS 5.1

[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_

SocketException - JK2, Tomcat 4.1.29, IIS 5.1

[Frank Febbraro]

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.socket:localhost:8009

# Uri mapping examples - jsp files only
#
[uri:/asis/*]
worker=ajp13:localhost:8009



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

Session Timeout / SocketException / Coyote

[christian . schuster]

Hi list,

I am sorry if this is an off topic. I am just not sure where my problem
really is located.

I have a web application which I start through web start. I do set the
session timeout to 30 min for security reasons. So when the session is
expired and the client tries to access again the server I sent back a
session expired object. On the client I can see that the object was read
from the input stream and that the stream is closed. I even can access some
stuff in that object. But on the server I get the following exception

Jul 17, 2003 5:25:12 PM
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler
processConnection
INFO: SocketException reading request, ignored

I also have the problem that my web application just hangs after this but
it does not by the same action and the server has still a valid session.

So, can my hanging application be connected to this Socket Exception
message?

Thanks for any info.

Christian Schuster

Rudolf Schuster AG
Postfach 277
CH - 3000 Bern 11

http://www.rsag.ch
++41 31 348 05 30


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

Re: HTTP10Interceptor: SocketException

[Bill Barker]

"Robert Irwin" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Thanks Bill,
>
> Followed the directions(thanks), no love...
>
> Same problem, HTTP10Interceptor: SocketException 6 times on close of
> browser.

Well, part of the instructions were to comment out the HTTP10Interceptor in
server.xml and use the CoyoteConnector instead ;-).  There aren't any fixes
to the HTTP10Interceptor in 3.3.2, since the plan is to deprecate it in
favor of the CoyoteConnector.  Note that the 3.3.2 CoyoteConnector is almost
the same code-base as the 4.1.x CoyoteConnector (the only difference is the
thin communications layer between Coyote and Tomcat).

> Would it be worth trying the 3.3.2 build?  Even though it's still a dev
> release?

The 3.3.2-dev is pretty stable (there haven't been any changes in months,
since it is considered feature-complete, and not many bugs get reported
against it anymore).  It is likely that the current nightly will become the
official 3.3.2 release when myself or Larry has enough spare time to
actually release it.  Most of the changes from 3.3.1->3.3.2 are pretty
obscure bug fixes.  And none of them relate to the Connectors.  As much as
I'd like people to try out 3.3.2, I don't think that you will see much of a
difference from the hybrid 3.3.1/Coyote.

>
> Thanks,
> truck
>
> - Original Message -
> From: "Bill Barker" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 26, 2003 9:24 PM
> Subject: Re: HTTP10Interceptor: SocketException
>
>
> > You could also try using the CoyoteConnector from 3.3.2-dev (fully
> > compatible with 3.3).
> > 
> >   1) Grab the 3.3.2-dev build from
> > http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/ and unpack
> into
> > a seperate directory.
> >   2) Follow the instructions at
> >
>
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/v1
> > .0-rc2/.  However don't use the jars from here, as this version is known
> to
> > be broken with TC 3.3.
> > 
> >
> >
> > "Robert Irwin" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> > Hello all, and any help please!
> >
> > Tomcat 3.3 on w2k server
> >
> > App throws the following when clients close browser window!  ANy help???
> > (yes, 6 or more times!)
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> >
> >
> >
> >
> > -
> > 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: HTTP10Interceptor: SocketException

[Robert Irwin]

Thanks Bill,

Followed the directions(thanks), no love...

Same problem, HTTP10Interceptor: SocketException 6 times on close of
browser.
Would it be worth trying the 3.3.2 build?  Even though it's still a dev
release?

Thanks,
truck

- Original Message -
From: "Bill Barker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 26, 2003 9:24 PM
Subject: Re: HTTP10Interceptor: SocketException


> You could also try using the CoyoteConnector from 3.3.2-dev (fully
> compatible with 3.3).
> 
>   1) Grab the 3.3.2-dev build from
> http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/ and unpack
into
> a seperate directory.
>   2) Follow the instructions at
>
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/v1
> .0-rc2/.  However don't use the jars from here, as this version is known
to
> be broken with TC 3.3.
> 
>
>
> "Robert Irwin" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> Hello all, and any help please!
>
> Tomcat 3.3 on w2k server
>
> App throws the following when clients close browser window!  ANy help???
> (yes, 6 or more times!)
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
>
>
>
>
> -
> 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: HTTP10Interceptor: SocketException

[Robert Irwin]

Thanks Filip, but I have a finicky audience, and they all will be running
local tomcat server.
They will be looking at the server window saying "Hey, this is wrong!!!"

I am wondering if there is something I need to do in my code to close the
socket?

The offending page contains: a form with input objects, xsl displaying data,
and an applet generating the client IP.
I have no idea which piece is giving me the trouble...

Thanks in advance...
 'Truck' Irwin


- Original Message -
From: "Filip Hanik" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Thursday, June 26, 2003 7:17 PM
Subject: RE: HTTP10Interceptor: SocketException


> that is ok, it was trying to read a socket (blocking io) and the socket
got
> closed
>
> Filip
>
> > -Original Message-
> > From: Robert Irwin [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, June 26, 2003 4:36 PM
> > To: [EMAIL PROTECTED]
> > Subject: HTTP10Interceptor: SocketException
> >
> >
> > Hello all, and any help please!
> >
> > Tomcat 3.3 on w2k server
> >
> > App throws the following when clients close browser window!  ANy
> > help???  (yes, 6 or more times!)
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
> > HTTP10Interceptor: SocketException reading request, ignored
> >
>
>
> -
> 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: HTTP10Interceptor: SocketException

[Bill Barker]

You could also try using the CoyoteConnector from 3.3.2-dev (fully
compatible with 3.3).

  1) Grab the 3.3.2-dev build from
http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/ and unpack into
a seperate directory.
  2) Follow the instructions at
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/v1
.0-rc2/.  However don't use the jars from here, as this version is known to
be broken with TC 3.3.



"Robert Irwin" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hello all, and any help please!

Tomcat 3.3 on w2k server

App throws the following when clients close browser window!  ANy help???
(yes, 6 or more times!)

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored





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

RE: HTTP10Interceptor: SocketException

[Filip Hanik]

that is ok, it was trying to read a socket (blocking io) and the socket got
closed

Filip

> -Original Message-
> From: Robert Irwin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 4:36 PM
> To: [EMAIL PROTECTED]
> Subject: HTTP10Interceptor: SocketException
>
>
> Hello all, and any help please!
>
> Tomcat 3.3 on w2k server
>
> App throws the following when clients close browser window!  ANy
> help???  (yes, 6 or more times!)
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>
> HTTP10Interceptor: SocketException reading request, ignored
>


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

HTTP10Interceptor: SocketException

[Robert Irwin]

Hello all, and any help please!

Tomcat 3.3 on w2k server

App throws the following when clients close browser window!  ANy help???  (yes, 6 or 
more times!)

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

HTTP10Interceptor: SocketException reading request, ignored

SocketException: Software caused connection abort

[Nibu-SP Thomas]

Hi,

Pls help me resolve the below problem with tomcat 3.2 on solaris 8. I'm getting this 
error very often after I upgraded to solaris 8
thanks in advance ...

java.net.SocketException: Software caused connection abort
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.socketAccept(Compiled Code)
at java.net.PlainSocketImpl.accept(Compiled Code)
at java.net.ServerSocket.implAccept(Compiled Code)
at java.net.ServerSocket.accept(Compiled Code)
at org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(Compiled Code)
at org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(Compiled Code)
at org.apache.tomcat.service.TcpListenerThread.run(Compiled Code)
at java.lang.Thread.run(Thread.java:479)
Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8090] shutdown due to 
exception: java.net.SocketException: Software caus
ed connection abort



--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.



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

Slightly OT: SocketException with MySQL

[Geoff Peters]

I am using Tomcat 4.1.18, MySQL 3.23, newest driver, running on Linux 7.3. Problem is 
similar to others who have posted on this subject, just want some advice (can't seem 
to get a definite answer). 

I'm not using connection pooling. If I walk away and leave the server running for 
several hours, I come back and cannot access the database via the servlet, the 
catalina.out file tells me "SQL Error: Communication link failure: 
java.net.SocketException". Happens whether or not I am running TOmcat remotely on or 
the same box as MySQL (i.e. not a network issue). I made sure all of my connection 
objects were close in the destroy() method of each servlet thinking all of the sockets 
were full, still didn't work. I just recently set autoReconnect = true in my 
server.xml realm tag - that doesn't seem to make a difference.  

Should that work? Or, should I be closing the connection object IMMEDIATELY after each 
executeUpdate or executeQuery? Currently am opening a connection in the init() method, 
and killing in the destroy(). 

Any suggestions greatly appreciated!! 

Thanks, Geoff 


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

RE: Tomcat 4.1.x and SocketException

[Luc Foisy]

Just tested this in RedHat 8.0 so its not likely related to the OS

Is it bad form for me to beg for help?? :)
Please please oh please!!

> -Original Message-
> From: Luc Foisy 
> Sent: Wednesday, December 18, 2002 10:36 AM
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4.1.x and SocketException
> 
> 
> 
> At the bottom of this mail is the output of a context 
> specific log, it shows an error that happens when I 
> continuously click on a link that loads another jsp page ( 
> hoping to simulate high volume traffic )
> I have been able to reproduce this on 4.1.12LE and 4.1.17LE 
> but not on 3.2.4 versions of tomcat. Also able to reproduce 
> on RedHat 7.0 and 7.3. JDK version is 1.4.0_03 and 1.4.0_02
> 
> Here is my context addition to server.xml ( pretty basic )
>   reloadable="true" crossContext="false">
> prefix="quick_log." suffix=".txt"
>   timestamp="true"/>
> 
> 
> All other configuration is default, just enough to get tomcat to run.
> 
> The actual web application did not seem to have a problem on 
> the front side. Everything went on as normal on 4.1.12
> Pages failed to be served correctly on 4.1.17 ( they are 
> blank ) though logging on with a new session will serve the 
> first couple pages then start blanking.
> 
> Months ago we attempted to upgrade to the 4.x version and 
> unknowly at that time this same error was happening in the 
> background. It eventually led to the server running out of 
> memory. Since not a single user was pounding away on the same 
> link, but probably because there was multiple users 
> contributing to the load.
> 
> I should mention that there is a mysql connection being used 
> at the application level that is being shared by all 
> sessions. The connection is used extensively throughout the 
> context. But I am fairly certain that this is not a mysql issue.
> 
> If I can provide any other information, let me know, I'd 
> really like to solve this problem as soon as possible...
> 
> Luc
> 
> --
> 
> 2002-12-18 09:52:38 StandardWrapperValve[jsp]: 
> Servlet.service() for servlet jsp threw exception
> org.apache.jasper.JasperException: Socket closed
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.java:248)
> at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:295)
> at 
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
> at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
> er(ApplicationFilterChain.java:247)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
> cationFilterChain.java:193)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
> rapperValve.java:260)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invokeNext(StandardPipeline.java:643)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardC
> ontextValve.java:191)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invokeNext(StandardPipeline.java:643)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at 
> org.apache.catalina.core.StandardContext.invoke(StandardContex
> t.java:2415)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHost
> Valve.java:180)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invokeNext(StandardPipeline.java:643)
> at 
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi
> spatcherValve.java:170)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invokeNext(StandardPipeline.java:641)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
> Valve.java:172)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invokeNext(StandardPipeline.java:641)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> 

Tomcat 4.1.x and SocketException

[Luc Foisy]

At the bottom of this mail is the output of a context specific log, it shows an error 
that happens when I continuously click on a link that loads another jsp page ( hoping 
to simulate high volume traffic )
I have been able to reproduce this on 4.1.12LE and 4.1.17LE but not on 3.2.4 versions 
of tomcat. Also able to reproduce on RedHat 7.0 and 7.3. JDK version is 1.4.0_03 and 
1.4.0_02

Here is my context addition to server.xml ( pretty basic )

  


All other configuration is default, just enough to get tomcat to run.

The actual web application did not seem to have a problem on the front side. 
Everything went on as normal on 4.1.12
Pages failed to be served correctly on 4.1.17 ( they are blank ) though logging on 
with a new session will serve the first couple pages then start blanking.

Months ago we attempted to upgrade to the 4.x version and unknowly at that time this 
same error was happening in the background. It eventually led to the server running 
out of memory. Since not a single user was pounding away on the same link, but 
probably because there was multiple users contributing to the load.

I should mention that there is a mysql connection being used at the application level 
that is being shared by all sessions. The connection is used extensively throughout 
the context. But I am fairly certain that this is not a mysql issue.

If I can provide any other information, let me know, I'd really like to solve this 
problem as soon as possible...

Luc

--

2002-12-18 09:52:38 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw 
exception
org.apache.jasper.JasperException: Socket closed
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:248)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.StandardContext.invoke(StandardContext.java:2415)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:174)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
at java.lang.Thread.run(Thread.java:536)
- Root Cause -
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.S

Re: SocketException

[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

[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

[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.

SocketException

[Ram Kochhar]

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:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Tomcat 4.1.12 on W2K (SP3) - SocketException: Socket operation on nonsocket

[Checkley, Ian [IBM GSA]]

Please help!

I have just installed Tomcat 4.1.12 on W2K (SP3) and when I attempt  to
connect to port 8080 I get java.net.SocketException: Socket operation on
nonsocket  (see stderr log below)

'netstat -a' lists a local process listening on port 8080

THANKS 
BFN ian C.
--
Created catalinaLoader in: C:\Program Files\Apache Group\Tomcat
4.1\server\lib
Sep 26, 2002 1:39:44 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Sep 26, 2002 1:39:45 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Sep 26, 2002 1:39:48 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Sep 26, 2002 1:39:53 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Sep 26, 2002 1:40:23 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Sep 26, 2002 1:40:23 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
Sep 26, 2002 1:40:23 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=10/300  config=C:\Program Files\Apache
Group\Tomcat 4.1\conf\jk2.properties
java.net.SocketException: Socket operation on nonsocket: setsockopt
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(Unknown Source)
at java.net.Socket.setSoLinger(Unknown Source)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.
java:414)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:507)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:533)
at java.lang.Thread.run(Unknown Source)
Sep 26, 2002 1:40:24 AM
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler
processConnection
INFO: SocketException reading request, ignored

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

Re: Message in logs: "Http10Interceptor: SocketException readingrequest, ignored"

[Bill Barker]

The most common reason for this is that the user hit the "stop" botton in
the browser before all of the "POST" data was read. Almost always, it is due
to a client action.

"Carlos J. Ramos" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> We have this estrange message in tomcat logs, it seems not to be quite
> important, because everything seems to work fine... did anybody knows
> the meaning of this message?
>
> 2002-09-09 17:55:18 - Http10Interceptor: SocketException reading
> request, ignored
>
> Thanks in advance.
>
> --
> 
> Carlos J. Ramos Genasys II Spain, S.A.U.
> Administrador de Sistemas Ventura de la Vega 5
> Tel:+34-91-3649100 ext 170 28014 Madrid
> Fax:+34-91-3649119 Spain
> Email:  [EMAIL PROTECTED]
> 





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

Message in logs: "Http10Interceptor: SocketException readingrequest, ignored"

[Carlos J. Ramos]

We have this estrange message in tomcat logs, it seems not to be quite
important, because everything seems to work fine... did anybody knows
the meaning of this message?

2002-09-09 17:55:18 - Http10Interceptor: SocketException reading
request, ignored

Thanks in advance.

-- 

Carlos J. Ramos Genasys II Spain, S.A.U.
Administrador de Sistemas   Ventura de la Vega 5
Tel:+34-91-3649100 ext 170  28014 Madrid
Fax:+34-91-3649119  Spain
Email:  [EMAIL PROTECTED]



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

FW: SocketException (Invalid arg) on Solaris

[Folbrecht, Paul]

I'll try this just once more- does anybody have any idea at all?

-Original Message-
From: Folbrecht, Paul [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 03, 2002 6:20 PM
To: Tomcat-User@Jakarta. Apache. Org (E-mail)
Subject: SocketException (Invalid arg) on Solaris


Running Tomcat 4.0.1 with JBoss 2.4.4 on Solaris 8 with Sun JDK 1.31.

We see this problem on a very sporadic basis - it appears from the trace
that perhaps Socket.setTcpNoDelay() isn't supported by this JDK, and Tomcat
is not prepared to handle that.

Anyway, there is a SocketException, and the reopen attempts fails.  I
suspect the reason for that is that either the socket was never closed or
for some other reason the OS is still has the port locked.

Anyway, the end result is that after this event the server no longer accepts
HTTP requests, obviously since the listener socket is dead.  The JBoss
console, however, can still be served at port 9082.

Haven't been able to find anything in the docs to explain this.  If someone
knows a workaround- including a version upgrade- please let us know.  TIA.

[ERROR,EmbeddedCatalinaServiceSX] HttpConnector[9080] accept: 
java.net.SocketException: Invalid argument
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:192)
at java.net.Socket.setTcpNoDelay(Socket.java:377)
at
org.apache.catalina.connector.http.HttpConnector.run(HttpConnector.java:984)
at java.lang.Thread.run(Thread.java:484)
[INFO,EmbeddedCatalinaServiceSX] HttpConnector[9080] Opening server socket
on all host IP addresses
[ERROR,EmbeddedCatalinaServiceSX] HttpConnector[9080] socket reopen: 
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:452)
at java.net.ServerSocket.(ServerSocket.java:170)
at java.net.ServerSocket.(ServerSocket.java:121)
at
org.apache.catalina.net.DefaultServerSocketFactory.createSocket(DefaultServe
rSocketFactory.java:118)
at
org.apache.catalina.connector.http.HttpConnector.open(HttpConnector.java:946
)
at
org.apache.catalina.connector.http.HttpConnector.run(HttpConnector.java:1001
)
at java.lang.Thread.run(Thread.java:484)





This transmission contains information solely for intended recipient and may
be privileged, confidential and/or otherwise protect from disclosure.  If
you are not the intended recipient, please contact the sender and delete all
copies of this transmission.  This message and/or the materials contained
herein are not an offer to sell, or a solicitation of an offer to buy, any
securities or other instruments.  The information has been obtained or
derived from sources believed by us to be reliable, but we do not represent
that it is accurate or complete.  Any opinions or estimates contained in
this information constitute our judgment as of this date and are subject to
change without notice.  Any information you share with us will be used in
the operation of our business, and we do not request and do not want any
material, nonpublic information. Absent an express prior written agreement,
we are not agreeing to treat any information confidentially and will use any
and all information and reserve the right to publish or disclose any
information you share with us.

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



This transmission contains information solely for intended recipient and may
be privileged, confidential and/or otherwise protect from disclosure.  If
you are not the intended recipient, please contact the sender and delete all
copies of this transmission.  This message and/or the materials contained
herein are not an offer to sell, or a solicitation of an offer to buy, any
securities or other instruments.  The information has been obtained or
derived from sources believed by us to be reliable, but we do not represent
that it is accurate or complete.  Any opinions or estimates contained in
this information constitute our judgment as of this date and are subject to
change without notice.  Any information you share with us will be used in
the operation of our business, and we do not request and do not want any
material, nonpublic information. Absent an express prior written agreement,
we are not agreeing to treat any information confidentially and will use any
and all information and reserve the right to publish or disclose any
information you share with us.

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

SocketException on closed socket causing memory leak

[Chris]

Using Tomcat 3.2.1/Sun's JRE 1.3.1_03

If a user makes two requests very quickly so the first request's socket
connection is closed, a subsequent forward of the request results in a
java.net.SocketException.  Well and good, I catch the exception.  Realizing
that
no response is possible, I log the error and basically do nothing.  The
second request is processed and all is well.

However, using JProbe's memory debugger, I have found that objects created
during the processing of the first request (the one whose socket connection
has been closed) are not being garbage collected.

In other words, if, during testing of the application, I make requests so as
not to cause an overrun, all memory is garbage collected as expected.
However, any overrun results in loitering objects.

Is there something that Tomcat wants or requires from me when this situation
occurs?  Any ideas?




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

SocketException (Invalid arg) on Solaris

[Folbrecht, Paul]

Running Tomcat 4.0.1 with JBoss 2.4.4 on Solaris 8 with Sun JDK 1.31.

We see this problem on a very sporadic basis - it appears from the trace
that perhaps Socket.setTcpNoDelay() isn't supported by this JDK, and Tomcat
is not prepared to handle that.

Anyway, there is a SocketException, and the reopen attempts fails.  I
suspect the reason for that is that either the socket was never closed or
for some other reason the OS is still has the port locked.

Anyway, the end result is that after this event the server no longer accepts
HTTP requests, obviously since the listener socket is dead.  The JBoss
console, however, can still be served at port 9082.

Haven't been able to find anything in the docs to explain this.  If someone
knows a workaround- including a version upgrade- please let us know.  TIA.

[ERROR,EmbeddedCatalinaServiceSX] HttpConnector[9080] accept: 
java.net.SocketException: Invalid argument
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:192)
at java.net.Socket.setTcpNoDelay(Socket.java:377)
at
org.apache.catalina.connector.http.HttpConnector.run(HttpConnector.java:984)
at java.lang.Thread.run(Thread.java:484)
[INFO,EmbeddedCatalinaServiceSX] HttpConnector[9080] Opening server socket
on all host IP addresses
[ERROR,EmbeddedCatalinaServiceSX] HttpConnector[9080] socket reopen: 
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:452)
at java.net.ServerSocket.(ServerSocket.java:170)
at java.net.ServerSocket.(ServerSocket.java:121)
at
org.apache.catalina.net.DefaultServerSocketFactory.createSocket(DefaultServe
rSocketFactory.java:118)
at
org.apache.catalina.connector.http.HttpConnector.open(HttpConnector.java:946
)
at
org.apache.catalina.connector.http.HttpConnector.run(HttpConnector.java:1001
)
at java.lang.Thread.run(Thread.java:484)





This transmission contains information solely for intended recipient and may
be privileged, confidential and/or otherwise protect from disclosure.  If
you are not the intended recipient, please contact the sender and delete all
copies of this transmission.  This message and/or the materials contained
herein are not an offer to sell, or a solicitation of an offer to buy, any
securities or other instruments.  The information has been obtained or
derived from sources believed by us to be reliable, but we do not represent
that it is accurate or complete.  Any opinions or estimates contained in
this information constitute our judgment as of this date and are subject to
change without notice.  Any information you share with us will be used in
the operation of our business, and we do not request and do not want any
material, nonpublic information. Absent an express prior written agreement,
we are not agreeing to treat any information confidentially and will use any
and all information and reserve the right to publish or disclose any
information you share with us.

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

Http10Interceptor: SocketException reading request, ignored

[Chris Gokey]

Hi...

Tomcat 3.3 has been behaving flawlessly for us recently until today,
suddenly we are getting:
Http10Interceptor: SocketException reading request, ignored

Any idea why one would get this error?

We recently had a publication go out regarding our system, so our load
is probably higher than normal.  Could this error be related to load?
Requests where taking < 1 second and now can take as many as 10 seconds,
although this behavior appears to be intermittent.

Thanks,
Chris



--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Re: RMI error (SocketException: socket write error) on Tomcat 4.0, NT4/Win2K

[Tee Chee Han]

I have found the solution. It turns out that RMI fails if Tomcat is installed in 
directory with white spaces. Before my original posting, I had actually seen 
this bug in the tomcat-dev mailing list:
http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg17201.html

But I thought my problem was a different one because the error mentioned in this 
bug report was one of MalformedURL. Out of desperation, I tried re-installing 
Tomcat in a directory without white space and now it works.

In any case, thanks RS.



cheehan


[EMAIL PROTECTED] wrote:

> Turn on logging on the RMI server process:
> 
> java  -Djava.rmi.server.logCalls=true -Djava.rmi.server.logLevel=VERBOSE
> -Djava.rmi.loader.logLevel=VERBOSE 
> 
> where,
> java.rmi.server.logCalls=true  -> will log all incoming calls and
> exceptions
> java.rmi.server.logLevel=VERBOSE -> will log details of outgoing calls
> java.rmi.loader.logLevel=VERBOSE -> logs classname and codebase whenever
> RMI attempts to load a class as aresult of
> unmarshalling an arg.
> 
> This could help in debugging.
> 
> Thanks.
> RS.
> 
> 
> 
> 
> 
> 
> Tee Chee Han <[EMAIL PROTECTED]> on 12/19/2001 04:47:18 AM
> 
> Please respond to "Tomcat Users List" <[EMAIL PROTECTED]>
> 
> To:   [EMAIL PROTECTED]
> cc:
> 
> Subject:  RMI error (SocketException: socket write error) on Tomcat 4.0,
>   NT4/Win2K
> 
> Hi,
> 
> -- Environment --
> I am running Tomcat 4.0.1 on NT4 with JDK1.3.0.
> 
> -- Error Symptom --
> I have a servlet that makes RMI calls to an RMI server process (non EJB) on
> the
> same machine. It used to work fine on Tomcat 3.2.3 and Tomcat 3.3 but when
> we
> switched to Tomcat 4.0 it stopped working.
> 
> The servlet looks-up the RMI server object successfully but fails as soon
> as it
> tries to invoke an RMI method with this exception:
> java.net.SocketException: Connection aborted by peer: socket write error
> [See end of message for full stack trace]
> 
> At first we suspected it had to do with the policy file but we have ruled
> that
> out because we are NOT running with the "-security" option and the error
> doesn't
> seem to point to a security or permission problem. It also doesn't seem
> like a
> CLASSPATH problem because everything else (including the RMI lookup) works
> fine.
> 
> I have scoured the web for a solution but found only an identical question
> on
> comp.lang.java with no reply.
> 
> Is Tomcat 4.0 doing anything different with RMI? Is JNDI or EJB somehow
> involved
> here by default? We don't use either of these.
> 
> Any help would be much appreciated!
> 
> 
> 
> cheehan
> 
> 
> -- Stack Trace --
> 
> java.rmi.MarshalException: error marshalling arguments; nested exception
> is:
>  java.net.SocketException: Connection aborted by peer: socket write
> error
> 
> java.net.SocketException: Connection aborted by peer: socket write error
>  at java.net.SocketOutputStream.socketWrite(Native Method)
>  at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
>  at
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:72
> )
>  at
> java.io.BufferedOutputStream.write(BufferedOutputStream.java:116)
>  at java.io.ObjectOutputStream.drain(ObjectOutputStream.java:1477)
>  at
> java.io.ObjectOutputStream.setBlockData(ObjectOutputStream.java:1500)
> 
>  at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:407)
>  at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:268)
>  at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:106)
>  at hello.ExecuterImpl_Stub.execute(Unknown Source)
> 
> [...]
> 
>  at hello.ServletA.doPost(Unknown Source)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:247)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:193)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:243)
>  at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
> .java:566)
>  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
> a:472)
>  at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java

Re: RMI error (SocketException: socket write error) on Tomcat 4.0, NT4/Win2K

[RSEQUEIRA]

Turn on logging on the RMI server process:

java  -Djava.rmi.server.logCalls=true -Djava.rmi.server.logLevel=VERBOSE
-Djava.rmi.loader.logLevel=VERBOSE 

where,
java.rmi.server.logCalls=true  -> will log all incoming calls and
exceptions
java.rmi.server.logLevel=VERBOSE -> will log details of outgoing calls
java.rmi.loader.logLevel=VERBOSE -> logs classname and codebase whenever
RMI attempts to load a class as aresult of
unmarshalling an arg.

This could help in debugging.

Thanks.
RS.






Tee Chee Han <[EMAIL PROTECTED]> on 12/19/2001 04:47:18 AM

Please respond to "Tomcat Users List" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:

Subject:  RMI error (SocketException: socket write error) on Tomcat 4.0,
  NT4/Win2K

Hi,

-- Environment --
I am running Tomcat 4.0.1 on NT4 with JDK1.3.0.

-- Error Symptom --
I have a servlet that makes RMI calls to an RMI server process (non EJB) on
the
same machine. It used to work fine on Tomcat 3.2.3 and Tomcat 3.3 but when
we
switched to Tomcat 4.0 it stopped working.

The servlet looks-up the RMI server object successfully but fails as soon
as it
tries to invoke an RMI method with this exception:
java.net.SocketException: Connection aborted by peer: socket write error
[See end of message for full stack trace]

At first we suspected it had to do with the policy file but we have ruled
that
out because we are NOT running with the "-security" option and the error
doesn't
seem to point to a security or permission problem. It also doesn't seem
like a
CLASSPATH problem because everything else (including the RMI lookup) works
fine.

I have scoured the web for a solution but found only an identical question
on
comp.lang.java with no reply.

Is Tomcat 4.0 doing anything different with RMI? Is JNDI or EJB somehow
involved
here by default? We don't use either of these.

Any help would be much appreciated!



cheehan


-- Stack Trace --

java.rmi.MarshalException: error marshalling arguments; nested exception
is:
 java.net.SocketException: Connection aborted by peer: socket write
error

java.net.SocketException: Connection aborted by peer: socket write error
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:72
)
 at
java.io.BufferedOutputStream.write(BufferedOutputStream.java:116)
 at java.io.ObjectOutputStream.drain(ObjectOutputStream.java:1477)
 at
java.io.ObjectOutputStream.setBlockData(ObjectOutputStream.java:1500)

 at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:407)
 at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:268)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:106)
 at hello.ExecuterImpl_Stub.execute(Unknown Source)

[...]

 at hello.ServletA.doPost(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:201)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve
.java:246)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

 at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2344)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:164)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:170)
 at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)

RMI error (SocketException: socket write error) on Tomcat 4.0, NT4/Win2K

[Tee Chee Han]

Hi,

-- Environment --
I am running Tomcat 4.0.1 on NT4 with JDK1.3.0.

-- Error Symptom --
I have a servlet that makes RMI calls to an RMI server process (non EJB) on the 
same machine. It used to work fine on Tomcat 3.2.3 and Tomcat 3.3 but when we 
switched to Tomcat 4.0 it stopped working.

The servlet looks-up the RMI server object successfully but fails as soon as it 
tries to invoke an RMI method with this exception:
java.net.SocketException: Connection aborted by peer: socket write error
[See end of message for full stack trace]

At first we suspected it had to do with the policy file but we have ruled that 
out because we are NOT running with the "-security" option and the error doesn't 
seem to point to a security or permission problem. It also doesn't seem like a 
CLASSPATH problem because everything else (including the RMI lookup) works fine.

I have scoured the web for a solution but found only an identical question on 
comp.lang.java with no reply.

Is Tomcat 4.0 doing anything different with RMI? Is JNDI or EJB somehow involved 
here by default? We don't use either of these.

Any help would be much appreciated!



cheehan


-- Stack Trace --

java.rmi.MarshalException: error marshalling arguments; nested exception is:
 java.net.SocketException: Connection aborted by peer: socket write error

java.net.SocketException: Connection aborted by peer: socket write error
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:72
)
 at java.io.BufferedOutputStream.write(BufferedOutputStream.java:116)
 at java.io.ObjectOutputStream.drain(ObjectOutputStream.java:1477)
 at java.io.ObjectOutputStream.setBlockData(ObjectOutputStream.java:1500)

 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:407)
 at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:268)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:106)
 at hello.ExecuterImpl_Stub.execute(Unknown Source)

[...]

 at hello.ServletA.doPost(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:201)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve
.java:246)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

 at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2344)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:164)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
 at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:
462)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at org.apache.catalina.valves.RequestFilterValve.process(RequestFilterVa
lve.java:324)
 at org.apache.catalina.valves.RemoteHostValve.invoke(RemoteHostValve.jav
a:131)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:163)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)

RE: Help needed: SocketException killing Tomcat 4.0.1 !?

[Brian Adams]

sounds like the sam problem I had when using mod_webapp  I reconfigured it
for good old jk_mod and all is well.
B

-Original Message-
From: Guillaume Mathe [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 10, 2001 2:32 AM
To: [EMAIL PROTECTED]
Subject: Help needed: SocketException killing Tomcat 4.0.1 !?


Hi again,

This post must have been lost in the flow... I really need help on that,
because a self-destructing Tomcat will not help me deploy my commercial
webapp...
Here's the setup:
- Tomcat 4.0.1, windows 98SE or 2000/Server
- Direct servlet access from port 8080
- JDK/JRE 1.3.1 from Sun or JRE 1.3.0 from IBM, tested both
- Also compiled with JDK1.4, just to make sure it's not my JDK
- Crash test servlet: a image/jpeg content-type servlet, using Sun's JPEG
codec. Using a BufferedOutputStream. The servlet works fine when called 
normally. (you can create a blank image, no need to draw anything - a wait
loop would be useful though...)

Crash test procedure:
- Open a browser and call the servlet. (with a  )
- BEFORE the servlet has finished encoding the JPEG, click on STOP, BACK, or
a link going elsewhere.

Result:
- A SocketException: connection reset by peer shows up, as expected.
- The exception is thrown  by out.close() ('out' being the
BufferedOutputStream given to the JpegEncoder) and is NOT catched by the
servlet ! quite 
unexpected...
- Catalina dies, now that is unexpected ! Logs generally do not reflect the
fatal exception.
- Under windows98SE it dies with a fatal error... 

My questions:
- Is it a *known* bug of Catalina ?
- If yes, has it been fixed in a recent build ?
- How can i trap this exception ? I want to handle properly client
disconnects by closing resources and stopping SQL queries etc... Currently
even if i put a 
catch() at each level up to GenericServlet, it goes through.

Regards,
Guillaume Mathe
Smartinnov


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

SocketException killing Tomcat 4.0.1 - more

[Guillaume Mathe]

Hi again,

I forgot a detail in my first post:
When it dies catalina causes exception c026H in module kernel32.dll.

Regards,
Guillaume Mathe
Smartinnov


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Help needed: SocketException killing Tomcat 4.0.1 !?

[Guillaume Mathe]

Hi again,

This post must have been lost in the flow... I really need help on that, because a 
self-destructing Tomcat will not help me deploy my commercial webapp...
Here's the setup:
- Tomcat 4.0.1, windows 98SE or 2000/Server
- Direct servlet access from port 8080
- JDK/JRE 1.3.1 from Sun or JRE 1.3.0 from IBM, tested both
- Also compiled with JDK1.4, just to make sure it's not my JDK
- Crash test servlet: a image/jpeg content-type servlet, using Sun's JPEG codec. Using 
a BufferedOutputStream. The servlet works fine when called 
normally. (you can create a blank image, no need to draw anything - a wait loop would 
be useful though...)

Crash test procedure:
- Open a browser and call the servlet. (with a  )
- BEFORE the servlet has finished encoding the JPEG, click on STOP, BACK, or a link 
going elsewhere.

Result:
- A SocketException: connection reset by peer shows up, as expected.
- The exception is thrown  by out.close() ('out' being the BufferedOutputStream given 
to the JpegEncoder) and is NOT catched by the servlet ! quite 
unexpected...
- Catalina dies, now that is unexpected ! Logs generally do not reflect the fatal 
exception.
- Under windows98SE it dies with a fatal error... 

My questions:
- Is it a *known* bug of Catalina ?
- If yes, has it been fixed in a recent build ?
- How can i trap this exception ? I want to handle properly client disconnects by 
closing resources and stopping SQL queries etc... Currently even if i put a 
catch() at each level up to GenericServlet, it goes through.

Regards,
Guillaume Mathe
Smartinnov


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Not in FAQ: SocketException killing Tomcat 4.0.1...

[Guillaume Mathe]

Hi,

Here's the setup:
- Tomcat 4.0.1, windows 98SE or 2000/Server
- Direct servlet access from port 8080
- JDK/JRE 1.3.1 from Sun or JRE 1.3.0 from IBM, tested both
- Also compiled with JDK1.4
- Test servlet: a image/jpeg content-type servlet, using Sun's JPEG codec. Using a 
BufferedOutputStream.

Test procedure:
- Open a browser and call the servlet.
- BEFORE the servlet has finished encoding the JPEG, click on STOP, BACK, or a link 
going elsewhere.

Result:
- A SocketException: connection reset by peer shows up, as expected.
- The exception is thrown  by out.close() ('out' being the BufferedOutputStream given 
to the JpegEncoder) and is NOT catched by the servlet ! quite 
unexpected...
- Catalina dies, now that is unexpected ! Logs generally do not reflect the fatal 
exception.
- Under windows98SE it dies with a fatal error... 

My questions:
- Is it a known bug of Catalina ?
- If yes, has it been fixed in a recent build ?
- Can i trap this exception ? I want to handle properly client disconnects by closing 
resources and stopping SQL queries etc...

Regards,
Guillaume Mathe
Smartinnov


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

SocketException: software caused connection abort

[Mapoteca Rio]

Hi all,

I have been experiencing the problem below using
Tomcat 3.1 (+ Apache 1.3.12 using mod_jserv) under
Solaris 8 and jdk 1.3.1.

java.net.SocketException: Software caused connection
abort
at
java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at
java.net.ServerSocket.implAccept(ServerSocket.java:243)
at
java.net.ServerSocket.accept(ServerSocket.java:222)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(SimpleTcpEnd
point.java:267)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(SimpleT
cpEndpoint.java:248)
at
org.apache.tomcat.service.TcpListenerThread.run(SimpleTcpEndpoint.jav
a:319)
at java.lang.Thread.run(Thread.java:484)
Endpoint
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
shutdown
due to
exception: java.net.SocketException: Software caused
connection abort

Tomcat server hangs up and doesn't respond to requests
anymore.

I have already seen a couple of messages describing
the same problem, but nobody answered. 

I am DESPERATE!!! Can anyone PLEASE help me??


__
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

SocketException : Software caused connection abort

[Mapoteca Rio]

Hi all,

I have been experiencing the problem below using
Tomcat 3.1 (+ Apache 1.3.12 using mod_jserv) under
Solaris 8 and jdk 1.3.1.

java.net.SocketException: Software caused connection
abort
at
java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at
java.net.ServerSocket.implAccept(ServerSocket.java:243)
at
java.net.ServerSocket.accept(ServerSocket.java:222)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(SimpleTcpEnd
point.java:267)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(SimpleT
cpEndpoint.java:248)
at
org.apache.tomcat.service.TcpListenerThread.run(SimpleTcpEndpoint.jav
a:319)
at java.lang.Thread.run(Thread.java:484)
Endpoint
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
shutdown
due to
exception: java.net.SocketException: Software caused
connection abort

Tomcat server hangs up and doesn't respond to requests
anymore.

I have already seen a couple of messages describing
the same problem, but nobody answered. 

I am DESPERATE!!! Can anyone PLEASE help me??

__
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

SocketException : Software caused connection abort

[stephane . senart]

Using any tomcat 3.1, 3.1.2, 3.2.3, I get the same socket exception after few
minutes of usage :

java.net.SocketException: Software caused connection abort
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(SimpleTcpEnd
point.java:267)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(SimpleT
cpEndpoint.java:248)
at
org.apache.tomcat.service.TcpListenerThread.run(SimpleTcpEndpoint.jav
a:319)
at java.lang.Thread.run(Thread.java:484)
Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] shutdown
due to
exception: java.net.SocketException: Software caused connection abort

Tomcat server hangs up and doesn't respond to requests anymore.
Our system is SUN Solaris 5.6 (patch level is fine). It happens on other similar
 server. This problem occurs on many projects around tomcat.

Is there anyone who manage to solve such a problem ?

 thanks,
 Stéphane SENART




Ce message peut contenir des informations confidentielles protegees
par le secret professionnel.
Si vous avez recu cet e-mail par erreur, nous vous remercions de bien
vouloir nous en aviser et de le detruire immediatement.

This message may contain privileged or confidential information.
If you have received this e-mail by mistake, please immediately notify
us and destroy it.

Credit Agricole Indosuez
==

RE: ContextManager: SocketException reading request, ignored

[Dan R. Labonte]

Anything behind curtain #1 or #2...

Truly the 100pts. just shows that you care about your fellow cohorts in
need. :-)
Dan

-Original Message-
From: Brett M. Bergquist [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 1:59 PM
To: [EMAIL PROTECTED]
Subject: Re: ContextManager: SocketException reading request, ignored 


No problem Dan.  I've received much help from others and am happy to
contribute where I can.
BTW, what does 100pts get me :)

- Original Message -
From: Dan R. Labonte <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 1:35 PM
Subject: RE: ContextManager: SocketException reading request, ignored


> Brett,
>
> I thank you for your expertise... Shutdown smoothly! You get 100pts. for
> your effort.
>
> Dan
>
> -Original Message-
> From: Brett M. Bergquist [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 23, 2001 1:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ContextManager: SocketException reading request, ignored
>
>
> Dan, I might be able to help on your second problem.  I've read and
> experienced that on HP-UX 11, that the there is an issue on closing a
socket
> with a read pending.  We have Tomcat 3.2 running on HP-UX 11 and I needed
to
> add the following to the line that starts Tomcat.  This is a parameter
> passed to the java jvm:
>
>  -XdoCloseWithReadPending
>
> You can search on "doCloseWithReadPending" on the HP site and see what
this
> relates to.
>
>
> - Original Message -
> From: Dan R. Labonte <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2001 12:46 PM
> Subject: RE: ContextManager: SocketException reading request, ignored
>
>
> > Any ideas?
> >
> >
> > So I was receiving the out of Buffer errors and the census was for me to
> > upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors
as
> of
> > yet. I do have two new issues now:
> >
> > 1. I'm receiving this error often:
> > $2001-08-21 15:56:29 - ContextManager: SocketException reading request,
> > ignored - java.net.SocketException: Connection refused: Connection
refused
> > at java.net.SocketInputStream.socketRead(Native Method)
> > at java.net.SocketInputStream.read(Unknown Source)
> > at java.io.BufferedInputStream.fill(Unknown Source)
> > at java.io.BufferedInputStream.read(Unknown Source)
> > at
> >
>
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
> > java:115)
> > at
> >
>
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
> > tStream.java:106)
> > at
> >
>
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
> > tream.java:128)
> > at
> > javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
> > at
> >
>
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
> > tAdapter.java:129)
> > at
> >
>
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> > onnectionHandler.java:198)
> > at
> >
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> > at
> >
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> > at java.lang.Thread.run(Unknown Source)
> >
> > 2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end
up
> > having to use the kill command.
> >
> > Here is the environment:
> >
> > HP-UX 11.00
> > JDK 1.3
> > Tomcat 3.2.3
> >
> > Any and all replies are welcomed
> > Thanks in advance,
> >
> > Dan
> >
>

Re: ContextManager: SocketException reading request, ignored

[Brett M. Bergquist]

No problem Dan.  I've received much help from others and am happy to
contribute where I can.
BTW, what does 100pts get me :)

- Original Message -
From: Dan R. Labonte <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 1:35 PM
Subject: RE: ContextManager: SocketException reading request, ignored


> Brett,
>
> I thank you for your expertise... Shutdown smoothly! You get 100pts. for
> your effort.
>
> Dan
>
> -Original Message-
> From: Brett M. Bergquist [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 23, 2001 1:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ContextManager: SocketException reading request, ignored
>
>
> Dan, I might be able to help on your second problem.  I've read and
> experienced that on HP-UX 11, that the there is an issue on closing a
socket
> with a read pending.  We have Tomcat 3.2 running on HP-UX 11 and I needed
to
> add the following to the line that starts Tomcat.  This is a parameter
> passed to the java jvm:
>
>  -XdoCloseWithReadPending
>
> You can search on "doCloseWithReadPending" on the HP site and see what
this
> relates to.
>
>
> - Original Message -
> From: Dan R. Labonte <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2001 12:46 PM
> Subject: RE: ContextManager: SocketException reading request, ignored
>
>
> > Any ideas?
> >
> >
> > So I was receiving the out of Buffer errors and the census was for me to
> > upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors
as
> of
> > yet. I do have two new issues now:
> >
> > 1. I'm receiving this error often:
> > $2001-08-21 15:56:29 - ContextManager: SocketException reading request,
> > ignored - java.net.SocketException: Connection refused: Connection
refused
> > at java.net.SocketInputStream.socketRead(Native Method)
> > at java.net.SocketInputStream.read(Unknown Source)
> > at java.io.BufferedInputStream.fill(Unknown Source)
> > at java.io.BufferedInputStream.read(Unknown Source)
> > at
> >
>
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
> > java:115)
> > at
> >
>
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
> > tStream.java:106)
> > at
> >
>
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
> > tream.java:128)
> > at
> > javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
> > at
> >
>
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
> > tAdapter.java:129)
> > at
> >
>
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> > onnectionHandler.java:198)
> > at
> >
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> > at
> >
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> > at java.lang.Thread.run(Unknown Source)
> >
> > 2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end
up
> > having to use the kill command.
> >
> > Here is the environment:
> >
> > HP-UX 11.00
> > JDK 1.3
> > Tomcat 3.2.3
> >
> > Any and all replies are welcomed
> > Thanks in advance,
> >
> > Dan
> >
>

RE: ContextManager: SocketException reading request, ignored

[Dan R. Labonte]

Brett,

I thank you for your expertise... Shutdown smoothly! You get 100pts. for
your effort.

Dan

-Original Message-
From: Brett M. Bergquist [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 1:24 PM
To: [EMAIL PROTECTED]
Subject: Re: ContextManager: SocketException reading request, ignored 


Dan, I might be able to help on your second problem.  I've read and
experienced that on HP-UX 11, that the there is an issue on closing a socket
with a read pending.  We have Tomcat 3.2 running on HP-UX 11 and I needed to
add the following to the line that starts Tomcat.  This is a parameter
passed to the java jvm:

 -XdoCloseWithReadPending

You can search on "doCloseWithReadPending" on the HP site and see what this
relates to.


- Original Message -
From: Dan R. Labonte <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 12:46 PM
Subject: RE: ContextManager: SocketException reading request, ignored


> Any ideas?
>
>
> So I was receiving the out of Buffer errors and the census was for me to
> upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors as
of
> yet. I do have two new issues now:
>
> 1. I'm receiving this error often:
> $2001-08-21 15:56:29 - ContextManager: SocketException reading request,
> ignored - java.net.SocketException: Connection refused: Connection refused
> at java.net.SocketInputStream.socketRead(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at
>
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
> java:115)
> at
>
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
> tStream.java:106)
> at
>
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
> tream.java:128)
> at
> javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
> at
>
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
> tAdapter.java:129)
> at
>
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:198)
> at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> at java.lang.Thread.run(Unknown Source)
>
> 2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end up
> having to use the kill command.
>
> Here is the environment:
>
> HP-UX 11.00
> JDK 1.3
> Tomcat 3.2.3
>
> Any and all replies are welcomed
> Thanks in advance,
>
> Dan
>

Re: ContextManager: SocketException reading request, ignored

[Brett M. Bergquist]

Dan, I might be able to help on your second problem.  I've read and
experienced that on HP-UX 11, that the there is an issue on closing a socket
with a read pending.  We have Tomcat 3.2 running on HP-UX 11 and I needed to
add the following to the line that starts Tomcat.  This is a parameter
passed to the java jvm:

 -XdoCloseWithReadPending

You can search on "doCloseWithReadPending" on the HP site and see what this
relates to.


- Original Message -
From: Dan R. Labonte <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 12:46 PM
Subject: RE: ContextManager: SocketException reading request, ignored


> Any ideas?
>
>
> So I was receiving the out of Buffer errors and the census was for me to
> upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors as
of
> yet. I do have two new issues now:
>
> 1. I'm receiving this error often:
> $2001-08-21 15:56:29 - ContextManager: SocketException reading request,
> ignored - java.net.SocketException: Connection refused: Connection refused
> at java.net.SocketInputStream.socketRead(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at
>
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
> java:115)
> at
>
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
> tStream.java:106)
> at
>
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
> tream.java:128)
> at
> javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
> at
>
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
> tAdapter.java:129)
> at
>
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:198)
> at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
> at java.lang.Thread.run(Unknown Source)
>
> 2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end up
> having to use the kill command.
>
> Here is the environment:
>
> HP-UX 11.00
> JDK 1.3
> Tomcat 3.2.3
>
> Any and all replies are welcomed
> Thanks in advance,
>
> Dan
>

RE: ContextManager: SocketException reading request, ignored

[Dan R. Labonte]

Any ideas? 


So I was receiving the out of Buffer errors and the census was for me to
upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors as of
yet. I do have two new issues now:

1. I'm receiving this error often:
$2001-08-21 15:56:29 - ContextManager: SocketException reading request,
ignored - java.net.SocketException: Connection refused: Connection refused
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
java:115)
at
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
tStream.java:106)
at
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
tream.java:128)
at
javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
at
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
tAdapter.java:129)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:198)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Unknown Source)

2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end up
having to use the kill command.

Here is the environment:

HP-UX 11.00
JDK 1.3
Tomcat 3.2.3

Any and all replies are welcomed
Thanks in advance,

Dan

ContextManager: SocketException reading request, ignored

[Dan R. Labonte]

So I was receiving the out of Buffer errors and the census was for me to
upgrade to Tomcat 3.2.3, which I did. So far so good, no Buffer errors as of
yet. I do have two new issues now:

1. I'm receiving this error often:
$2001-08-21 15:56:29 - ContextManager: SocketException reading request,
ignored - java.net.SocketException: Connection refused: Connection refused
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.
java:115)
at
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
tStream.java:106)
at
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
tream.java:128)
at
javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
at
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpReques
tAdapter.java:129)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:198)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Unknown Source)

2. When I try to shutdown Tomcat with tomcat.sh it never dies and I end up
having to use the kill command.

Here is the environment:

HP-UX 11.00
JDK 1.3
Tomcat 3.2.3

Any and all replies are welcomed
Thanks in advance,

Dan

ContextManager: SocketException reading request

[Don Wee]

Can someone help here? I just start to use Tomcat 
with Apache on NetWare server. And sometimes when the servlet reads html form 
request, tomcat shows the "ContextManager: SocketException reading request". 
Please see the following for detail message. The environment I'm using is 
Tomcat3.2.2, Apache1.3.20 and NetWare5.1. Thanks in advance!
 
Tomcat shows:
ContextManager: SocketException reading request, 
ignored
    java.net.SocketException: socket 
available: Socket operation on non-socket
        
        at 
java.net.PlainSocketImpl.socketAvailable(Native Method)
        
        at 
java.net.PlainSocketImpl.available(Unknown Source)
    
at java.net.SocketInputStream.available(Unknown Source)
        
        at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:217)
        
        at 
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
        
        at 
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
        
        at java.lang.Thread.run(Unknown 
Source)
 
 
 

SocketException 10055

[Pavel Drasil]

Hello,

I have been using Tomcat for some time (with Win95) and everything was
OK. But yesterday I ran some program that misconfigured my system somehow
and now I can't start Tomcat - it ends with a "SocketException: listen
failed (code=10055)" message. Don't you know what that code means and what
to do?

Thank You

Pavel Drasil

Re: SocketException

[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();
,

SocketException

[Enrique Cea]

Hello.

Im testing a Java application that connects to a servlet and send it some objects, 
then the server connects to a RMI remote object and do some tasks on it.

I think everything is well configured but get this exception when trying to connect to 
the server:

-- Exception -

2001-05-26 12:39:02 - 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(HttpRequestAdapter.java:115)
at 
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInputStream.java:106)
at 
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputStream.java:128)
at javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
at 
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpRequestAdapter.java:129)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:195)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)

 /Exception --

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();

--- /code of the client --

and the code of the servlet is

-- code of the servlet --

public void doPost( HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException
{
ObjectInputStream in = new ObjectInputStream(req.getInputStream());

try {

Mensaje mensaje = (Mensaje) in.readObject();
int foro = (int) in.readInt();

//The parent class of this server connects to a RMI Servidor object
//and asings it to servidro object

servidor.anyadirMensaje(mensaje, foro);



} catch (Exception e) {
e.printStackTrace();
}

in.close();

}

-- /code of the servlet --


Thank you in advance and sorry for having to send this big post.

ArrayIndexOutOfBoundsException & SocketException

[Metodi Mladenov]

Hi,
 
I am new to 
Tomcat.
I am trying to start 
it on Linux but I am receiving the following errors:
 
 
 
[metodim@p200lxmm 
bin]$ ./startup.shGuessing TOMCAT_HOME from tomcat.sh to ./..Setting 
TOMCAT_HOME to ./..Using classpath: 
./../lib/ant.jar:./../lib/build.xml:./../lib/jasper.jar:./../lib/jaxp.jar:./../lib/parser.jar:./../lib/servlet.jar:./../lib/test:./../lib/webserver.jar[metodim@p200lxmm 
bin]$ 2001-05-10 04:57:18 - ContextManager: Adding context Ctx( /examples 
)2001-05-10 04:57:19 - ContextManager: Adding context Ctx( /admin 
)Starting tomcat. Check logs/tomcat.log for error messages2001-05-10 
04:57:19 - ContextManager: Adding context Ctx(  )2001-05-10 04:57:19 - 
ContextManager: Adding context Ctx( /test )2001-05-10 04:57:23 - 
PoolTcpConnector: Starting HttpConnectionHandler on 80802001-05-10 04:57:23 
- PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007
 
When I try to 
connect to htpp://p200lxmm:8080/examples I am receiving 
java.lang.ArrayIndexOutOfBoundsException
 
And when I try to 
shutdown the server I am receiving the following:
 
[metodim@p200lxmm 
bin]$ ./shutdown.shGuessing TOMCAT_HOME from tomcat.sh to ./..Setting 
TOMCAT_HOME to ./..Using classpath: 
./../lib/ant.jar:./../lib/build.xml:./../lib/jasper.jar:./../lib/jaxp.jar:./../lib/parser.jar:./../lib/servlet.jar:./../lib/test:./../lib/webserver.jarStop 
tomcatHANDLER THREAD PROBLEM: java.net.SocketException: Invalid 
argumentjava.net.SocketException: Invalid 
argument    at 
java.net.PlainSocketImpl.socketSetOption(PlainSocketImpl.java:native)    
at 
java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:158)    
at 
java.net.Socket.setSoLinger(Socket.java:106)    
at 
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:122)    
at 
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)    
at 
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)    
at java.lang.Thread.run(Thread.java:325)[metodim@p200lxmm 
bin]$
 
One more question! 
It seems that the server don't create tomcat.log file because I couldn't find it 
anywhere.
 
Can somebody give me 
some guidelines how to proceed?
 
Regards,
Metodi

Http10Interceptor: SocketException reading request,

[Danny Angus]

I've noticed that:

2001-04-12 13:58:07 - Http10Interceptor: SocketException reading request,
ignored

looks like it might be accompanied by a step up in memory use (linux rh6,
JVM=jre1.3.0_02,java -server option), and that memory use doesn't come down
with load. is this a bug?

RE: SocketException with Tomcat 3.2.1

[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
> 
> 

SocketException with Tomcat 3.2.1

[joeri]

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(HttpRequestAdapter.java:115)
 at
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInputStream.java:106)
 at
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputStream.java:128)
 at
javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
 at
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpRequestAdapter.java:129)
 at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:195)
 at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
 at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.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

Context Manager - SocketException

[Amir Nuri]

Hi

Does Anyone knows why what this exception means ???, and why do i get it ???
(I'm useing tomcat3.2)

ContextManager: SocketException reading request, ignored -
java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAvailable(Native Method)
at java.net.PlainSocketImpl.available(PlainSocketImpl.java:451)
at java.net.SocketInputStream.available(SocketInputStream.java:137)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
   onnectionHandler.java:214)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)


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

Context Manager - SocketException

[Amir Nuri]

Hi

Does Anyone knows why what this exception means ???, and why do i get it ???
(I'm useing tomcat3.2)

ContextManager: SocketException reading request, ignored -
java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAvailable(Native Method)
at java.net.PlainSocketImpl.available(PlainSocketImpl.java:451)
at java.net.SocketInputStream.available(SocketInputStream.java:137)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
   onnectionHandler.java:214)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)


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

SocketException on Linux JDK1.3 Tomcat3.1

[Stéphane Laurière]

Hello,
I'm using Tomcat successfully as standalone jsp/servlet server on WindowsNT
with no reboot from the server during several weeks.
However I'm facing big problems on Linux Mandrake, JDK1.3 by Sun, Tomcat3.1
running as standalone
server: I sometimes get a SocketException that makes the server shut down
whereas there are a maximum of two concurrent connections to the server. The
main pb is Tomcat not only misses the connection, it also crashes
completely.
I have pasted the stack trace below. Has any of you already faced such a pb?
Thanks,
Stéphane


java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(SimpleTcpEndpoint.j
ava:267)
at
org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(SimpleTcpEndpo
int.java:248)
at
org.apache.tomcat.service.TcpListenerThread.run(SimpleTcpEndpoint.java:319)
at java.lang.Thread.run(Thread.java:484)
Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] shutdown
due to exception: java.net.SocketException: Connection reset by peer