Forwarded, did not get through, and I really wonder why!

Jacques

----- Original Message ----- From: "Jacques Le Roux" <[email protected]>
To: <[email protected]>
Sent: Sunday, June 13, 2010 4:23 PM
Subject: Re: Trund demo


I have decided to put it in even if I agree with Scott that it seems out of 
subject.
But as from your experience it solved an issue, I prefer to try for sometimes on the demo trunk and if Scott is right (which so far seems logically to be more than possible) I will revert. Actually following Scott's advice I should better put an HTTPD before a local instance an then try locally (because HTTPD seems involved in this) but I have no time to play with that at the moment.
That's why I decided to commit: to try with the demo trunk where I 1st saw this 
issue

Jacques

From: "BJ Freeman" <[email protected]>
what it achieves as I have said all along is that it stops the error from 
happening so I can see the real error.
you seem stuck on the fact it is a not in ofbiz.
so I don't see how we will come to a consensus.

bottom line is I have used the patch  it solve a problem I am happy.
I shared this and it is up to others to decide if they want to try it.


Scott Gray sent the following on 6/12/2010 7:47 PM:


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  
<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialty market.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>

Then there is a problem with your setup, my guess is that you have a misconfigured apache server in front of OFBiz that is prematurely closing the connection. But that is just a guess.

All that adding /error to the allowed paths has done is to allow clients to request that URL (http://domain/webapp/error/*) and that achieves nothing.

Regards
Scott

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

I got neither of the pages you put up.
only in the log files.

not sure how ClientAbortExceptions got thrown in the mix.
I am talking about try catch with a throwable exception.

=========================
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 6:13 PM:
I'm going to take some guesses here about what you are actually talking about.

This is what a webapp with an error page looks like:
http://imgur.com/GFMBY.png

This is what a webapp with a missing error page looks like:
http://imgur.com/BlAPU.png

For the second case, this error occurs when error/error.jsp (this is the default, it can be changed in the controller) is missing from the webapp, it has nothing to do with the allowed paths. When this error occurs then yes, it can hide the actual exception that was thrown, but no, your patch does nothing to fix this.

And once again, this has absolutely nothing to do with ClientAbortExceptions.

Regards
Scott

On 13/06/2010, at 12:56 PM, Scott Gray wrote:

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











Reply via email to