Forwarded, did not get through, and I really wonder why!
Jacques
- Original Message -
From: Jacques Le Roux jacques.le.r...@les7arts.com
To: user@ofbiz.apache.org
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
jacques.le.r...@les7arts.com
To: user@ofbiz.apache.org
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
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
to follow up on it is my configiration.
you will note the orginal email was about the trunk demo having a error
of broken pipes.
so you have a test bed to figure out what was misconfigured, or caused
that error.
=
BJ Freeman
http://bjfreeman.elance.com
Strategic Power
Hi BJ,
Could you make a patch for that?
TIA
Jacques
From: Jacques Le Roux jacques.le.r...@les7arts.com
Looks like this would be a valuable contribution!
Jacques
From: BJ Freeman bjf...@free-man.net
my gues is this error is caused by not having and error path in the
web.xml and it is
not sure a patch is the real answer.
should visit why the code errors when it can't find the path, since the
path has never been supplied.
it would mean a more intelligent check, like do I really need this path.
or even just remove the code that looks for the path.
=
BJ
on second thought not a good idea to remove code since that is part of
the web-app spec.
=
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation
http://www.businessesnetwork.com/automation/viewforum.php?f=52
Specialtymarket.com
https://issues.apache.org/jira/browse/OFBIZ-3820
Jacques Le Roux sent the following on 6/12/2010 3:12 AM:
Hi BJ,
Could you make a patch for that?
TIA
Jacques
From: Jacques Le Roux jacques.le.r...@les7arts.com
Looks like this would be a valuable contribution!
Jacques
From: BJ Freeman
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
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.
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
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
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.
here is the error log from 9.04
2010-04-25 13:22:48,076 (TP-Processor12) [
ControlServlet.java:246:ERROR] An error
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
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
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
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:
my gues is this error is caused by not having and error path in the
web.xml and it is covering up the real error.
scott and I had some discussion on this, I solved it by a global replace
and added the error path to all components web.xml.
now I get errors that are traceable.
Looks like this would be a valuable contribution!
Jacques
From: BJ Freeman bjf...@free-man.net
my gues is this error is caused by not having and error path in the
web.xml and it is covering up the real error.
scott and I had some discussion on this, I solved it by a global replace
and added
19 matches
Mail list logo
