You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Susan Hoddinott <su...@hexworx.com> on 2003/12/03 04:15:50 UTC
Socket write error 10022
Hello,
I recently upgraded my java JVM from an earlier version of 1.3.1 to 1.3.1_09. I found when I did this that some things which were previously working now give the following error:
//////////////////////////////////////////////////////////////
MonitorFilter::IOExceptionMonitorFilter::A web application object caused an exception
MonitorFilter::java.net.SocketException: socket write error (code=10022)
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:91)
at org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:679)
at org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:741)
at org.apache.catalina.connector.ResponseBase.write(ResponseBase.java:652)
at org.apache.catalina.connector.ResponseStream.write(ResponseStream.java:312)
at org.apache.catalina.connector.http.HttpResponseStream.write(HttpResponseStream.java:175)
at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1893)
at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1642)
at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1194)
at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519)
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(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:223)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:142)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: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.java:164)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java: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.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106)
//////////////////////////////////////////////////////////////////////////////////////
I tried 1.3.1_08 and it did the same thing. As the errors are clearly Tomcat related, is there something in my Tomcat configuration I also need to change? Does anyone know what this error is and how it may be fixed?
Regards,
Susan Hoddinott
http://www.hexworx.com
Re: Tunning up Tomcat to run web application on desktops in the single
user environment with limitted resources
Posted by Tim Funk <fu...@joedog.org>.
You can probably delete the following from server/lib
servlets-invoker.jar ( And remove from web.xml)
servlets-manager.jar (Unless you *need* the manager)
servlets-webdav.jar
# Only keep the connectors that you plan on using
tomcat-coyote.jar
tomcat-http11.jar
tomcat-jk.jar
tomcat-jk2.jar
tomcat-warp.jar
In web.xml, comment out jsp servlet and remove jasper-compiler.jar from
common/lib
If you don't need the manager, admin, to compile jsp (which you don't since
they are precompiled), I think you might be able to get away with removing
all ant related jars too.
-Tim
Kris Gemborys wrote:
> First I want to apologize for another of these mails "what is better
> jetty vs tomcat' but most of the available resources compare both
> containers in the environment where they are serving multiple concurrent
> requests. What I am interested is the container that utilizes as little
> resources as possible and is the most responsive while running on
> Pentium III or low-end Pentium 4 laptop with small amount of RAM serving
> single user. My limited knowledge about both products does not allow me
> to perform any type of container configuration beyond of lowering
> maximum number of threads for jetty.
>
> Here is what I have done so far and my results:
> Windows XP Professional/Pentium 4 M - 2 Ghz/Tomcat 4.1.24/Jetty
> 4.2.15/JDK 1.4.1
> Prototype application uses XSLT/XML/Cloudscape with no connection pooling
>
> I removed all preinstalled Tomcat web applications except Manager.
> I also removed bunch of other files from Jetty, Tomcat and SUN's JDK
> packages which helped me to create two distributable 20 MB zips for both
> JDK/Tomcat and JDK/ Jetty.
> I deployed a prototype application to both Jetty and Tomcat.
> I precompiled all jsp for both Jetty and Tomcat - fortunately they both
> are using jasper :-)
> I have observed that Jetty starts and loads application at least twice
> faster and uses 25% less memory. The pages were rendered within 1 sec.
> I am not using <load-on-startup>. to conserve RAM.
>
> Does anybody have comments on this topic?
> Are there any Tomcat specific hints to improve its performance and
> reduce amount of utilized resources assuming that it is being used by a
> single user?
>
> Thanks for help, Kris.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Tunning up Tomcat to run web application on desktops in the single
user environment with limitted resources
Posted by Kris Gemborys <ma...@comcast.net>.
First I want to apologize for another of these mails "what is better
jetty vs tomcat' but most of the available resources compare both
containers in the environment where they are serving multiple concurrent
requests. What I am interested is the container that utilizes as little
resources as possible and is the most responsive while running on
Pentium III or low-end Pentium 4 laptop with small amount of RAM serving
single user. My limited knowledge about both products does not allow me
to perform any type of container configuration beyond of lowering
maximum number of threads for jetty.
Here is what I have done so far and my results:
Windows XP Professional/Pentium 4 M - 2 Ghz/Tomcat 4.1.24/Jetty
4.2.15/JDK 1.4.1
Prototype application uses XSLT/XML/Cloudscape with no connection pooling
I removed all preinstalled Tomcat web applications except Manager.
I also removed bunch of other files from Jetty, Tomcat and SUN's JDK
packages which helped me to create two distributable 20 MB zips for both
JDK/Tomcat and JDK/ Jetty.
I deployed a prototype application to both Jetty and Tomcat.
I precompiled all jsp for both Jetty and Tomcat - fortunately they both
are using jasper :-)
I have observed that Jetty starts and loads application at least twice
faster and uses 25% less memory. The pages were rendered within 1 sec.
I am not using <load-on-startup>. to conserve RAM.
Does anybody have comments on this topic?
Are there any Tomcat specific hints to improve its performance and
reduce amount of utilized resources assuming that it is being used by a
single user?
Thanks for help, Kris.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Socket write error 10022
Posted by Susan Hoddinott <su...@hexworx.com>.
No. This is not the problem. This is occurring at the testing stage and no
stop button is being pressed.
Regards,
Susan Hoddinott
http://www.hexworx.com
----- Original Message -----
From: "Bill Barker" <wb...@wilshire.com>
To: <to...@jakarta.apache.org>
Sent: Wednesday, December 03, 2003 2:32 PM
Subject: Re: Socket write error 10022
If this isn't in the FAQ already, it should be ;-).
SocketWriteErrors are almost always the result of the user hitting the
"stop" button in the browser before the page is fully loaded. The "fix" is
to make your content more interesting, so users stop doing this, or to make
it load faster so that they don't get the chance ;-).
"Susan Hoddinott" <su...@hexworx.com> wrote in message
news:006401c3b94b$c2f7a080$1f84fea9@shoddino...
Hello,
I recently upgraded my java JVM from an earlier version of 1.3.1 to
1.3.1_09. I found when I did this that some things which were previously
working now give the following error:
//////////////////////////////////////////////////////////////
MonitorFilter::IOExceptionMonitorFilter::A web application object caused
an exception
MonitorFilter::java.net.SocketException: socket write error (code=10022)
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:91)
at
org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:679
)
at
org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.
java:741)
at org.apache.catalina.connector.ResponseBase.write(ResponseBase.java:652)
at
org.apache.catalina.connector.ResponseStream.write(ResponseStream.java:312)
at
org.apache.catalina.connector.http.HttpResponseStream.write(HttpResponseStre
am.java:175)
at
org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:18
93)
at
org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1642)
at
org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.jav
a:1194)
at
org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519)
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
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter
.java:223)
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:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:201)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.j
ava:142)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: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.java:164
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:462)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:163)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1011)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106
)
////////////////////////////////////////////////////////////////////////////
//////////
I tried 1.3.1_08 and it did the same thing. As the errors are clearly
Tomcat related, is there something in my Tomcat configuration I also need to
change? Does anyone know what this error is and how it may be fixed?
Regards,
Susan Hoddinott
http://www.hexworx.com
----------------------------------------------------------------------------
--
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Socket write error 10022
Posted by Bill Barker <wb...@wilshire.com>.
If this isn't in the FAQ already, it should be ;-).
SocketWriteErrors are almost always the result of the user hitting the "stop" button in the browser before the page is fully loaded. The "fix" is to make your content more interesting, so users stop doing this, or to make it load faster so that they don't get the chance ;-).
"Susan Hoddinott" <su...@hexworx.com> wrote in message news:006401c3b94b$c2f7a080$1f84fea9@shoddino...
Hello,
I recently upgraded my java JVM from an earlier version of 1.3.1 to 1.3.1_09. I found when I did this that some things which were previously working now give the following error:
//////////////////////////////////////////////////////////////
MonitorFilter::IOExceptionMonitorFilter::A web application object caused an exception
MonitorFilter::java.net.SocketException: socket write error (code=10022)
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:91)
at org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:679)
at org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:741)
at org.apache.catalina.connector.ResponseBase.write(ResponseBase.java:652)
at org.apache.catalina.connector.ResponseStream.write(ResponseStream.java:312)
at org.apache.catalina.connector.http.HttpResponseStream.write(HttpResponseStream.java:175)
at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1893)
at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1642)
at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1194)
at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519)
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(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:223)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:142)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: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.java:164)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java: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.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106)
//////////////////////////////////////////////////////////////////////////////////////
I tried 1.3.1_08 and it did the same thing. As the errors are clearly Tomcat related, is there something in my Tomcat configuration I also need to change? Does anyone know what this error is and how it may be fixed?
Regards,
Susan Hoddinott
http://www.hexworx.com
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org