Re: [djatoka-devel] frequent 500s - restart clears things for a few days
Status: Beta
Brought to you by:
rchute
From: Ryan C. <rc...@gm...> - 2009-12-08 02:46:38
|
Hi Phil, Searching around a bit more using "WARNING: Error sending end packet java.net.SocketException: Connection reset" as my term search seems to indicate that the client browser is prematurely closing the outputstream. This is the same as what I said before, but this time a site refers to Internet Explorer as the culprit, see below. Any chance you have IE clients using the djatoka viewer at the time of the SocketExceptions? The Apache logs may also have some error codes around the time of the exceptions. You can try turning up the djatoka log4.properties to DEBUG (located in adore-djatoka/WEB-INF/classes/), additionally might see if anything is being thrown to the Apache error.log. Let me know what you find. Thanks, Ryan From: http://www.4java.ca/faq.html#q37 Q: Broken Pipe Exception - What to do? A: We had a user experiencing a 'Broken pipe exception'2002-11-28 21:58:11 Ajp13Processor[8197][1] process: invoke java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) This is from a posting we found on the net which best explains the problem: "... In my experience those broken pipe errors seem to happen most often when Internet Exploder decided that the page hasn't changed. It looks like this may happen when the client drops the connection before the request is complete, and should generally be harmless ..." On Mon, Dec 7, 2009 at 5:43 PM, phil cryer <ph...@cr...> wrote: > Turn up debugging on Tomcat? djatoka? Apache? If so, where should I set that? > > For now I have Apache using AJP proxy to proxy requests to the tomcat > backends. In server.xml I have: > > <!-- Define an AJP 1.3 Connector on port 8009 --> > <Connector port="8009" > enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> > > which sends it back to Apache, and in Apache, I have the following in > /etc/apache2/conf.d/proxy_ajp > > ProxyPass /adore-djatoka/ ajp://127.0.0.1:8009/adore-djatoka/ smax=5 > max=20 ttl=120 retry=300 > ProxyPassReverse /adore-djatoka/ ajp://127.0.0.1:8009/adore-djatoka/ > > ProxyPass /djatoka/ ajp://127.0.0.1:8009/djatoka/ smax=5 max=20 > ttl=120 retry=300 > ProxyPassReverse /djatoka/ ajp://127.0.0.1:8009/djatoka/ > > Everything look in order? I don't remember when the smax, max, ttl > and retry lines were added, right now I deal with that via haproxy > upstream from the server. > > Thanks > > P > > > On Thu, Dec 3, 2009 at 11:15 AM, Ryan Chute <rc...@gm...> wrote: >> Hi Phil, >> >> These are not expected, but I'm not exactly sure why they just started >> happening. From what I can tell, these seem to happen when Apache >> drops the connection before Tomcat can completely return the requested >> resource. The exception looks to happen in the apache httpd/tomcat >> bridge, would you mind turning the debug level up to see if we can get >> a bit more context? >> >> Thanks, >> Ryan >> >> On Wed, Dec 2, 2009 at 2:57 PM, phil cryer <ph...@cr...> wrote: >>> I'm getting 500s, four today, and it seems to happen like this once a >>> week; a restart of Tomcat and things are fine for another week or >>> more. The check that is running against this server runs from inside >>> our network and hits our Prod box, on the same network, as well as a >>> mirror box on a different network. The mirror is always fine, it's >>> the Prod box that keeps having this issue. I've attached part of >>> today's catalina log (the full is 1.7M and is online here: >>> http://mbgserv18.mobot.org/tmp/catalina.2009-12-02.log), and you see >>> the same 'broken pipe' errors over and over. Are these expected? I >>> remember seeing things here and there, but this looks pretty regular. >>> Let me know if we need to turn up debugging to dig deeper. >>> >>> Thanks >>> >>> P >>> -- >>> http://philcryer.com >>> >>> ------------------------------------------------------------------------------ >>> Join us December 9, 2009 for the Red Hat Virtual Experience, >>> a free event focused on virtualization and cloud computing. >>> Attend in-depth sessions from your desk. Your couch. Anywhere. >>> http://p.sf.net/sfu/redhat-sfdev2dev >>> _______________________________________________ >>> djatoka-devel mailing list >>> dja...@li... >>> https://lists.sourceforge.net/lists/listinfo/djatoka-devel >>> >>> >> > > > > -- > http://philcryer.com > |