Comments inline...
Greg Hamer wrote:
Gentleman,
Should I be concerned about the following warning that I am seeing in my ApplicationContext log following application startup?:
ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
The full log from startup follows at the end. I am running Roller v1.2 on
Tomcat 5.5 on Windows XP.
Note, the warning is recorded in the log when the first user logs in. (In the
log below, there is an 8 minute time difference between startup and the warning
being recorded.) Also, I start Tomcat at the command line and the message is
not displayed in the stdout.
I suspect the causes of the first exception and the other (MediaCast)
one are different.
In your logs you show:
Oct 21, 2005 5:43:44 AM org.apache.catalina.core.StandardHostValve status
WARNING: Exception Processing ErrorPage[errorCode=404, location=/error404.jsp]
just before the ClientAbortException stack trace. This looks like a bug in the
error404.jsp page (which you may have customized, or it may be a bug in the
Roller distribution copy of this page). It isn't expected in two senses.
First, we shouldn't be getting a 404 error here; it suggests that there may be
an incorrect URL in some initial redirect/forwarding logic you're using.
Second, we shouldn't be getting an exception while processing the error page
when we do get the 404. The ClientAbortException here may be the client
browser balking at whatever it is getting at that point. More generally, it
indicates the browser has closed its socket while the server is still trying to
send.
If it happens in a stock (not customized) Roller install, please file a bug.
If you're using any of your own redirects, then setting up access logging in
Tomcat should provide more clues about the URLs Tomcat is seeing in requests.
I suspect that the MediaCast exception probably has a different underlying
cause; it looks more like a Roller bug. More info is needed to look at that.
Does it happen consistently on a given URL? You can file this on our JIRA with
example URLs and exception log content and we'll look into it.
--a
Generally, the server works fine. This error does reoccur, however, in some cases where users set MediaCast values on
weblog entries. In those cases the same warning appears in the log coincident with the user receiving the message
"MediaCast URL is not valid" when they "Post to Weblog". In these cases, the message
"MediaCast URL is not valid" is a false error. I say a "false error" because in these cases the
urls specified for the MediaCast value work fine when browsed directly.
g
localhost.2005-10-21.log
Oct 21, 2005 5:35:41 AM org.apache.catalina.core.ApplicationContext log
INFO: Use of the properties initialization parameter 'properties' has been
deprecated by 'org.apache.velocity.properties'
Oct 21, 2005 5:35:43 AM org.apache.catalina.core.ApplicationContext log
INFO: Use of the properties initialization parameter 'properties' has been
deprecated by 'org.apache.velocity.properties'
Oct 21, 2005 5:35:43 AM org.apache.catalina.core.ApplicationContext log
INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
[org.apache.webapp.balancer.RuleChain:
[org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News /
Redirect URL: http://www.cnn.com],
[org.apache.webapp.balancer.rules.RequestParameterRule: Target param name:
paramName / Target param value: paramValue / Redirect URL:
http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule:
Redirect URL: http://jakarta.apache.org]]
Oct 21, 2005 5:35:44 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Oct 21, 2005 5:35:44 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Oct 21, 2005 5:35:44 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Oct 21, 2005 5:35:44 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Oct 21, 2005 5:43:44 AM org.apache.catalina.core.StandardHostValve status
WARNING: Exception Processing ErrorPage[errorCode=404, location=/error404.jsp]
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error
at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
at
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
at org.apache.catalina.connector.Response.flushBuffer(Response.java:534)
at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:285)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
