On 13/06/2010, at 2:13 PM, BJ Freeman wrote:

> 
> yup but there are two ends to the stream in short when the exception is 
> thrown it stop the stream from ofbiz end cause the rest of info about the 
> real error to be lost.

Perhaps you didn't read the link I sent you:
"Wrap an IOException identifying it as being caused by an abort of a request by 
a remote client."
Abort of a request by a remote client, not by OFBiz or Tomcat.

> 
> here is the error log from 9.04
> 2010-04-25 13:22:48,076 (TP-Processor12) [
> ControlServlet.java:246:ERROR] An error occurred, going to the
> errorPage: /error/error.jsp
> 2010-04-25 13:22:48,096 (TP-Processor12) [
> ControlServlet.java:253:ERROR] Including errorPage: /error/error.jsp
> 2010-04-25 13:22:48,124 (TP-Processor12) [
> ServerHitBin.java:627:INFO ] Visit delegatorName=default, ServerHitBin
> delegatorName=default
> 2010-04-25 13:22:48,129 (TP-Processor12) [
> ControlServlet.java:327:INFO ] [[[main] Request Done- total:0.668,since
> last([main] Request Be...):0.668]]
> 2010-04-25 13:22:48,132 (TP-Processor12) [
> MsgContext.java:306:WARN ] Error sending end packet
> java.net.SocketException: Broken pipe
> 
> the key is
> ControlServlet.java:246:ERROR] An error occurred, going to the
> errorPage: /error/error.jsp
> [ControlServlet.java:253:ERROR] Including errorPage: /error/error.jsp

The key?  That second debug line actually means that OFBiz did find the error 
page and managed to get a RequestDispatcher for it.  This is the opposite to 
the "key" of your argument.

> the line nummber in the trunk are 221 and 228
> Now up at 212 an error page has been created with the real error.
> 
>       if (errorPage != null) {
> 221            Debug.logError("An error occurred, going to the errorPage: " + 
> errorPage, module);
> 
> 228                 Debug.logError("Including errorPage: " + errorPage, 
> module);
> 
> then we get into a try catch the stops the process. since the error path is 
> not avalible, there is no error reported on the webpages, just the log files.

The error page is available otherwise we never would have made it to line 228.

> now how to cause them, oops don't remember. been a few weeks since I fixed it 
> and don't have the in my memory.
> 
> I blieve one was caused by not finding a resource for uilables.
> 
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation  
> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com  <http://www.specialtymarket.com/>
> 
> Systems Integrator-- Glad to Assist
> 
> Chat  Y! messenger: bjfr33man
> Linkedin 
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
> 
> 
> Scott Gray sent the following on 6/12/2010 5:56 PM:
>> http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/connector/ClientAbortException.html
>> 
>> Please provide some steps to reproduce the problem you are describing so 
>> that I can see how adding the error directory to the list of allowed paths 
>> makes any difference whatsoever.
>> 
>> Thanks
>> Scott
>> 
>> On 13/06/2010, at 12:51 PM, BJ Freeman wrote:
>> 
>>> I beg to differ with you about it being the browser.
>>> I have tested this many times.
>>> 
>>> I do agree, as I said, it covers up the real error. so it is not the root 
>>> but a camouflage of the problem.
>>> 
>>> and my patch does not solve anything about the real problem on allows use 
>>> to see it.
>>> 
>>> =========================
>>> BJ Freeman
>>> http://bjfreeman.elance.com
>>> Strategic Power Office with Supplier 
>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>> 
>>> Systems Integrator-- Glad to Assist
>>> 
>>> Chat  Y! messenger: bjfr33man
>>> Linkedin<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>>> 
>>> 
>>> Scott Gray sent the following on 6/12/2010 3:55 PM:
>>>> That error has nothing to do with whatever was wrong with the instance.
>>>> 
>>>> It simply means that the browser requesting the page on that thread was 
>>>> either closed or was stopped by the user, so when OFBiz tried to send the 
>>>> response it couldn't because the connection had been closed.
>>>> 
>>>> It is a common exception and certainly not the root of any problems.
>>>> 
>>>> Regards
>>>> Scott
>>>> 
>>>> On 11/06/2010, at 7:46 PM, Jacques Le Roux wrote:
>>>> 
>>>>> I had to kill an reload the trunk demo this morning
>>>>> 
>>>>> We got this error
>>>>> 
>>>>> 010-06-11 08:44:28,177 (TP-Processor2) [     
>>>>> ControlServlet.java:230:ERROR] ---- exception report 
>>>>> ----------------------------------------------------------
>>>>> Error in request handler: Exception: 
>>>>> org.apache.catalina.connector.ClientAbortException
>>>>> Message: null
>>>>> ---- cause 
>>>>> ---------------------------------------------------------------------
>>>>> Exception: java.net.SocketException
>>>>> Message: Broken pipe
>>>>> ---- stack trace 
>>>>> ---------------------------------------------------------------
>>>>> java.net.SocketException: Broken pipe
>>>>> java.net.SocketOutputStream.socketWrite0(Native Method)
>>>>> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>>>>> java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>>>>> org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:532)
>>>>> org.apache.jk.common.JkInputStream.doWrite(JkInputStream.java:162)
>>>>> org.apache.coyote.Response.doWrite(Response.java:560)
>>>>> org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353)
>>>>> org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
>>>>> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309)
>>>>> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
>>>>> org.apache.catalina.connector.Response.flushBuffer(Response.java:548)
>>>>> org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:279)
>>>>> org.ofbiz.webapp.control.RequestHandler.renderView(RequestHandler.java:848)
>>>>> org.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:559)
>>>>> org.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:227)
>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
>>>>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
>>>>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
>>>>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
>>>>> org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
>>>>> org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
>>>>> org.apache.jsp.index_jsp._jspService(index_jsp.java:56)
>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>>> org.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:268)
>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>>>>> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>>>>> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>>>>> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>>>>> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>>>>> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>>>>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>>>>> java.lang.Thread.run(Thread.java:619)
>>>>> 
>>>>> 
>>>>> Jacques
>>>>> 
>>>> 
>>> 
>> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to