Yes, the pages do appear to render correctly - and no stop button activity involved; I've noticed it happening more frequently, though, as more entries have been added to the planet groups - thus I wondered if something of the TCP timeout vs. Roller variety. What about the possible / apparent Hibernate / PostgreSQL connection leakage - is that something you've ever seen or experienced under similar circumstances? -- Steve
>-----Original Message----- >From: Dave [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 5, 2006 07:02 AM >To: [email protected] >Subject: Re: Broken Pipe - Jboss 4.0.4 - Roller 3.0 > >That looks like the kind of message you get when somebody clicks the >stop button on the browser while loading your page. > >What happens when that errors occurs, does the page render correctly? > >- Dave > > > >On 12/4/06, Steve Wells <[EMAIL PROTECTED]> wrote: >> 1) I'm getting the following exception when displaying a page containing >> planet feed data. Any ideas? Is this something more general about tcp >> connections (ie flush vs no flush on jsps or something?) >> >> 2) It seems when this happens, I'm losing hibernate / postgresql dbms >> connections; is the equivalent of the Spring Hibernate connection cleanup >> filter used with Roller - if not, can it be & if / as so, what servlets >> should it service? >> >> ----------------- >> >> 2006-12-04 20:03:57,137 DEBUG >> [org.acegisecurity.ui.ExceptionTranslationFilter] Chain processed normally >> 2006-12-04 20:03:57,137 DEBUG >> [org.acegisecurity.context.HttpSessionContextIntegrationFilter] >> SecurityContextHolder set to new context, as request processing completed >> 2006-12-04 20:03:57,150 WARN >> [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost]] Exception >> Processing ErrorPage[errorCode=404, location=/WEB-INF/jsps/404.jsp] >> ClientAbortException: java.net.SocketException: Broken pipe >> 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:544) >> at >> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286) >> 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:868) >> at >> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663) >> at >> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) >> at >> org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) >> at java.lang.Thread.run(Thread.java:595) >> Caused by: java.net.SocketException: Broken pipe >> 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.realWriteBytes(InternalOutputBuffer.java:747) >> at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:403) >> at >> org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:305) >> at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:990) >> at org.apache.coyote.Response.action(Response.java:182) >> at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:322) >> ... 12 more >> >> >> >> >
