You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by fengjun <fe...@solutions.sh> on 2005/10/10 07:17:08 UTC
How can I combine the roller to my web application as the only one ?
Hi:
How can I combine the roller to my web application as the only one ?
Thanks
--
fengjun <fe...@solutions.sh>
Re: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
Posted by Dave Johnson <da...@rollerweblogger.org>.
At one point, the only way to shut off those client abort exceptions
was to set Velocity logging to FATAL errors only. This is probably
worth another look.
- Dave
On Oct 23, 2005, at 2:23 PM, Anil Gangolli wrote:
> Gili wrote:
>
>>
>> BTW, generally speaking, server applications should silently
>> ignore ClientAbortException and not log them.
>>
>> Gili
>>
>
> Yes, perhaps. I'm putting this on the dev list for input.
>
> We have some settings in our log4j.properties to avoid Velocity
> shouting about ClientAbortExceptions, which are 90+% of the time
> independent of server behavior. However, our default settings don't
> change anything in the Tomcat category for it. Should we? or should
> we really leave this up to the site administrator?
>
> --a
>
Re: ClientAbortException: java.net.SocketException: Software caused
connection abort: socket write error
Posted by Anil Gangolli <an...@busybuddha.org>.
Gili wrote:
>
> BTW, generally speaking, server applications should silently
> ignore ClientAbortException and not log them.
>
> Gili
>
Yes, perhaps. I'm putting this on the dev list for input.
We have some settings in our log4j.properties to avoid Velocity shouting
about ClientAbortExceptions, which are 90+% of the time independent of
server behavior. However, our default settings don't change anything
in the Tomcat category for it. Should we? or should we really leave
this up to the site administrator?
--a
Re: ClientAbortException: java.net.SocketException: Software caused
connection abort: socket write error
Posted by Gili <co...@bbs.darktech.org>.
BTW, generally speaking, server applications should silently ignore
ClientAbortException and not log them.
Gili
Anil Gangolli wrote:
>
> To set the log level for a given logger/ log category, you edit
> WEB-INF/classes/log4j.properties file within the exploded Roller web
> app. By convention, the log categories are the fully qualified class
> names of the class from which the logging is done. Whole packages can
> be enabled by using the package name.
>
> So by adding/editing a line of the form
>
> log4j.category.class.or.package.name=LEVEL
>
> (where you replace "class.or.package.name" with the qualified class or
> package name you want and LEVEL with the level (e.g. DEBUG) that you
> want, will set the level for that class or package.
> You'll see some examples in the shipped log4j.properties.
> --a.
>
> Greg Hamer wrote:
>
>> Anil,
>>
>> Thank you for getting back to me.
>>
>> Our Roller server is a stock install so I have filed bug ROL-850 in
>> JIRA for the ClientAbortException on login.
>>
>> Regarding the MediaCast exception, I will research it further, write
>> it up and file it in the JIRA. Yes, it does happen consistently with
>> certain URLs so I will include those urls in the bug report..
>> Regarding the MediaCast exceptions, could you advise me how to enable
>> debug logging? I ask because I see statements in the code executing
>> both mLogger.error() and mLogger.debug(). The code that I looked at is
>> based on the following error() that is both in the roller.log and in
>> the stdout: ERROR 2005-10-13 23:33:11,250
>> WeblogEntryFormAction:checkMediaCast - ERROR checking MediaCast URL
>> Looking at the source for the indicated method (checkMediaCast() on
>> WeblogEntryFormAction), I see that it includes logic to execute both
>> mLogger.error() and mLogger.debug(). However, as our server is
>> currently configured I am seeing no debug() messages.
>> fyi ... we will be upgrading our server as soon as Roller 1.3 is
>> released.
>> Thank you again for your assistance. In case I do not hear back from
>> you today, I hope that you will have an enjoyable weekend.
>>
>> Best regards,
>>
>> g
>>
>>
>
>
--
http://www.desktopbeautifier.com/
Re: ClientAbortException: java.net.SocketException: Software caused
connection abort: socket write error
Posted by Anil Gangolli <an...@busybuddha.org>.
To set the log level for a given logger/ log category, you edit
WEB-INF/classes/log4j.properties file within the exploded Roller web
app. By convention, the log categories are the fully qualified class
names of the class from which the logging is done. Whole packages can
be enabled by using the package name.
So by adding/editing a line of the form
log4j.category.class.or.package.name=LEVEL
(where you replace "class.or.package.name" with the qualified class or
package name you want and LEVEL with the level (e.g. DEBUG) that you
want, will set the level for that class or package.
You'll see some examples in the shipped log4j.properties.
--a.
Greg Hamer wrote:
>Anil,
>
>Thank you for getting back to me.
>
>Our Roller server is a stock install so I have filed bug ROL-850 in JIRA for the ClientAbortException on login.
>
>Regarding the MediaCast exception, I will research it further, write it up and file it in the JIRA. Yes, it does happen consistently with certain URLs so I will include those urls in the bug report..
>
>Regarding the MediaCast exceptions, could you advise me how to enable debug logging? I ask because I see statements in the code executing both mLogger.error() and mLogger.debug(). The code that I looked at is based on the following error() that is both in the roller.log and in the stdout:
> ERROR 2005-10-13 23:33:11,250 WeblogEntryFormAction:checkMediaCast - ERROR checking MediaCast URL
>Looking at the source for the indicated method (checkMediaCast() on WeblogEntryFormAction), I see that it includes logic to execute both mLogger.error() and mLogger.debug(). However, as our server is currently configured I am seeing no debug() messages.
>
>fyi ... we will be upgrading our server as soon as Roller 1.3 is released.
>
>Thank you again for your assistance. In case I do not hear back from you today, I hope that you will have an enjoyable weekend.
>
>Best regards,
>
>g
>
>
Re: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
Posted by Greg Hamer <ro...@gmail.com>.
Anil,
Thank you for getting back to me.
Our Roller server is a stock install so I have filed bug ROL-850 in JIRA for the ClientAbortException on login.
Regarding the MediaCast exception, I will research it further, write it up and file it in the JIRA. Yes, it does happen consistently with certain URLs so I will include those urls in the bug report..
Regarding the MediaCast exceptions, could you advise me how to enable debug logging? I ask because I see statements in the code executing both mLogger.error() and mLogger.debug(). The code that I looked at is based on the following error() that is both in the roller.log and in the stdout:
ERROR 2005-10-13 23:33:11,250 WeblogEntryFormAction:checkMediaCast - ERROR checking MediaCast URL
Looking at the source for the indicated method (checkMediaCast() on WeblogEntryFormAction), I see that it includes logic to execute both mLogger.error() and mLogger.debug(). However, as our server is currently configured I am seeing no debug() messages.
fyi ... we will be upgrading our server as soon as Roller 1.3 is released.
Thank you again for your assistance. In case I do not hear back from you today, I hope that you will have an enjoyable weekend.
Best regards,
g
Re: MediaCast and error404.jsp Bug?
Posted by Greg Hamer <ro...@gmail.com>.
Dave,
Thank you for the data from the debugger. It helped us to resolved a problem that we had misdiagnosed.
We addressed the problem we had experienced by correcting code on the server the MediaCast urls referenced which also were not including content-length in the HTTP HEADs. I am sorry that I was unable to provide MediaCast urls to that server, but it currently is not accessible from the public Internet.
Thank you again for your great work and the work of all of the Roller Team!
Best regards,
g
----- Original Message -----
From: "Dave Johnson" <da...@rollerweblogger.org>
To: <ro...@incubator.apache.org>
Sent: Sunday, October 23, 2005 1:01 PM
Subject: Re: MediaCast and error404.jsp Bug?
Greg,
When you enter a Podcast URL in a blog entry, Roller uses HTTP HEAD (via
the Java class HttpURLConnection) to query the URL to obtain the
content-type and content-length.
I tried each of the URLs you specified (which BTW are all web pages, not
"media" files) and stopped Roller in the debugger. All of those URLs are
returning a -1 content type, so Roller treats them as invalid (I believe the
enclosure tag needs both content-type and content-length). I'm not sure why
they return -1, I guess that means the websites are not returning
content-lengths at all.
So, I don't think this is a Roller MediaCast bug, but perhaps we could add
better error messages.
- Dave
Re: MediaCast and error404.jsp Bug?
Posted by Dave Johnson <da...@rollerweblogger.org>.
Greg,
When you enter a Podcast URL in a blog entry, Roller uses HTTP HEAD
(via the Java class HttpURLConnection) to query the URL to obtain the
content-type and content-length.
I tried each of the URLs you specified (which BTW are all web pages,
not "media" files) and stopped Roller in the debugger. All of those
URLs are returning a -1 content type, so Roller treats them as invalid
(I believe the enclosure tag needs both content-type and
content-length). I'm not sure why they return -1, I guess that means
the websites are not returning content-lengths at all.
So, I don't think this is a Roller MediaCast bug, but perhaps we could
add better error messages.
- Dave
On Oct 23, 2005, at 11:32 AM, Greg Hamer wrote:
> Anil,
>
> Following below is a draft of the proposed bug to be filed in the JIRA
> for the MediaCast exceptions that I mentioned in my email Friday.
> Toward the end are 4 URLs that are resulting in exceptions on our
> Roller v1.2 server. Could you please test these URLs by entering them
> as MediaCast values for a weblog entry on your server? If these URLs
> do result in exceptions on your configuration then I will file the
> bug. fyi, as indicated below under the heading "Additional Tests" we
> did deploy a second Roller 1.2 build and experienced substantially
> the same behavior.
>
> If you do not experience exceptions on your configuration, I would
> certainly welcome your suggestions ;-)
>
> Best regards,
>
> g
>
>
> DRAFT BUG REPORT
> ================
>
> We are using a stock install of Roller v1.2. (roller-1.2.tar.gz)
>
> When setting MediaCast values in "Edit Weblog", for certain urls the
> following message is returned after selecting "Post to Weblog":
> "MediaCast URL is not valid"
>
> We believe that for these urls the message "MediaCast URL is not
> valid" may be a false error. This is because the urls entered as
> MediaCast values can be successfully browsed directly in a browser.
>
> A further concern is that even though "MediaCast URL is not valid" is
> being displayed in the "Edit Weblog" page, no errors are being
> displayed in the stdout or recorded in roller.log. This is a concern
> because in the case of truly invalid urls, messages such as the
> following are both displayed in stdout and recorded in roller.log:
> ERROR 2005-10-13 18:10:31,890 WeblogEntryFormAction:checkMediaCast -
> ERROR checking MediaCast URL
> ERROR 2005-10-13 20:33:09,375 WeblogEntryFormAction:checkMediaCast -
> ERROR 405 return from MediaCast URL
> What we are seeing coincident with the "MediaCast URL is not valid"
> errors are errors in the ApplicationContext log. The errors in the
> ApplicationContext log do not appear coincident with 100% of the
> occurrences of the "MediaCast URL is not valid" errors being
> displayed. These coincident errors in the ApplicationContext log do,
> however, occur in the preponderance of the cases (e.g. > 80%). The
> errors in the ApplicationContext log are as follows:
> Oct 22, 2005 3:15:54 PM 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.jav
> a:285)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav
> a:136)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav
> a: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.process
> Connection(Http11Protocol.java:744)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoin
> t.java:527)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollo
> werWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo
> l.java:684)
> at java.lang.Thread.run(Unknown Source)
>
> Note: What may be a related bug has been filed in the JIRA as ROL-850.
>
> Following below are four urls that result in the error "MediaCast URL
> is not valid" (along with the frequently coincident error indicated in
> the ApplicationContext log). Of the urls below, only the first one
> returns an mp3 file. Note: Per the current draft of Roller's
> UserGuide20 the MediaCast setting adds the MediaCast url as an
> <enclosure> to the user's RSS newsfeed for that weblog entry. The
> current draft of UserGuide20 further states (under section [3.2]
> Podcasting with Roller):
> "We call it mediacasting in the Roller UI because it can be any type
> of file and is not necessarily destined for play on an Apple iPod."
>
> URLs
>
> http://dw.com.com/redir?&destUrl=http%3a%2f%2fmusic-
> files.download.com%2fsd%2fa4Gc-OTtTxN3HUnfc1Qz-
> OcZRBDKmYqpZjnZg4KA2kKhFDKHVArjpNqgqpB7zBIVtR6qsISG7C5txGnwYSuihb-
> EO50cVmWM%2fmp3download%2f100078411%2f192%2fONOFFON-
> Mardi_Gras.mp3&edId=3
>
> http://www.macromedia.com/index.html
>
> http://www.macromedia.com/cfusion/store/index.cfm?store=OLS-US
>
> http://forta.com/books/exam.cfm
>
>
> ADDITIONAL TESTS
>
> For further testing, we did a build of Roller 1.2 (using
> roller-src-1.2.tar.gz). We experienced substantially the same
> behavior with this second instance with two notable differences.
>
> First, in "Edit Weblog" the message returned upon selecting "Post to
> Weblog" was different. Rather than the messge "MediaCast URL is not
> valid", we received the message "Problem processing MediaCast, invalid
> URL?" Note these messages were still accompanied by the coincident
> errors in the ApplicationContext log originally reported. Based on
> our limited testing, the coincidence of the errors on the second
> instance was 100%.
>
> Second, with every "Post to Weblog" the following info messages were
> displayed in both the stdout and added to roller.log:
> INFO 2005-10-22 18:43:36,883 | WriteToIndexOperation:run | Starting
> search index operation
> INFO 2005-10-22 18:43:37,321 | WriteToIndexOperation:run | Search
> index operation complete
> Two additional notes on these info messages. First, in our test case
> both of these info messages were displayed regardless whether the
> MediaCast url was accepted or not. Second, in our primary server
> these info messages are never displayed upon selecting "Post to
> Weblog".
MediaCast and error404.jsp Bug?
Posted by Greg Hamer <ro...@gmail.com>.
Anil,
Following below is a draft of the proposed bug to be filed in the JIRA for the MediaCast exceptions that I mentioned in my email Friday. Toward the end are 4 URLs that are resulting in exceptions on our Roller v1.2 server. Could you please test these URLs by entering them as MediaCast values for a weblog entry on your server? If these URLs do result in exceptions on your configuration then I will file the bug. fyi, as indicated below under the heading "Additional Tests" we did deploy a second Roller 1.2 build and experienced substantially the same behavior.
If you do not experience exceptions on your configuration, I would certainly welcome your suggestions ;-)
Best regards,
g
DRAFT BUG REPORT
================
We are using a stock install of Roller v1.2. (roller-1.2.tar.gz)
When setting MediaCast values in "Edit Weblog", for certain urls the following message is returned after selecting "Post to Weblog": "MediaCast URL is not valid"
We believe that for these urls the message "MediaCast URL is not valid" may be a false error. This is because the urls entered as MediaCast values can be successfully browsed directly in a browser.
A further concern is that even though "MediaCast URL is not valid" is being displayed in the "Edit Weblog" page, no errors are being displayed in the stdout or recorded in roller.log. This is a concern because in the case of truly invalid urls, messages such as the following are both displayed in stdout and recorded in roller.log:
ERROR 2005-10-13 18:10:31,890 WeblogEntryFormAction:checkMediaCast - ERROR checking MediaCast URL
ERROR 2005-10-13 20:33:09,375 WeblogEntryFormAction:checkMediaCast - ERROR 405 return from MediaCast URL
What we are seeing coincident with the "MediaCast URL is not valid" errors are errors in the ApplicationContext log. The errors in the ApplicationContext log do not appear coincident with 100% of the occurrences of the "MediaCast URL is not valid" errors being displayed. These coincident errors in the ApplicationContext log do, however, occur in the preponderance of the cases (e.g. > 80%). The errors in the ApplicationContext log are as follows:
Oct 22, 2005 3:15:54 PM 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)
Note: What may be a related bug has been filed in the JIRA as ROL-850.
Following below are four urls that result in the error "MediaCast URL is not valid" (along with the frequently coincident error indicated in the ApplicationContext log). Of the urls below, only the first one returns an mp3 file. Note: Per the current draft of Roller's UserGuide20 the MediaCast setting adds the MediaCast url as an <enclosure> to the user's RSS newsfeed for that weblog entry. The current draft of UserGuide20 further states (under section [3.2] Podcasting with Roller):
"We call it mediacasting in the Roller UI because it can be any type of file and is not necessarily destined for play on an Apple iPod."
URLs
http://dw.com.com/redir?&destUrl=http%3a%2f%2fmusic-files.download.com%2fsd%2fa4Gc-OTtTxN3HUnfc1Qz-OcZRBDKmYqpZjnZg4KA2kKhFDKHVArjpNqgqpB7zBIVtR6qsISG7C5txGnwYSuihb-EO50cVmWM%2fmp3download%2f100078411%2f192%2fONOFFON-Mardi_Gras.mp3&edId=3
http://www.macromedia.com/index.html
http://www.macromedia.com/cfusion/store/index.cfm?store=OLS-US
http://forta.com/books/exam.cfm
ADDITIONAL TESTS
For further testing, we did a build of Roller 1.2 (using roller-src-1.2.tar.gz). We experienced substantially the same behavior with this second instance with two notable differences.
First, in "Edit Weblog" the message returned upon selecting "Post to Weblog" was different. Rather than the messge "MediaCast URL is not valid", we received the message "Problem processing MediaCast, invalid URL?" Note these messages were still accompanied by the coincident errors in the ApplicationContext log originally reported. Based on our limited testing, the coincidence of the errors on the second instance was 100%.
Second, with every "Post to Weblog" the following info messages were displayed in both the stdout and added to roller.log:
INFO 2005-10-22 18:43:36,883 | WriteToIndexOperation:run | Starting search index operation
INFO 2005-10-22 18:43:37,321 | WriteToIndexOperation:run | Search index operation complete
Two additional notes on these info messages. First, in our test case both of these info messages were displayed regardless whether the MediaCast url was accepted or not. Second, in our primary server these info messages are never displayed upon selecting "Post to Weblog".
Re: ClientAbortException: java.net.SocketException: Software caused
connection abort: socket write error
Posted by Anil Gangolli <an...@busybuddha.org>.
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)
>
>
>
ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
Posted by Greg Hamer <ro...@gmail.com>.
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.
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)