You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2002/10/22 20:46:07 UTC
DO NOT REPLY [Bug 13845] -
Axis logs/prints and exception when it shouldn't
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845
Axis logs/prints and exception when it shouldn't
------- Additional Comments From stevel@apache.org 2002-10-22 18:46 -------
We are going to have to distinguish genuine method raised faults from unexpected
something-went-wrong with the invocation faults, then.
How do you propose we do this?
Re: DO NOT REPLY [Bug 13845] - Axis logs/prints and exception when it shouldn't
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Richard Sitze" <rs...@us.ibm.com>
To: <ax...@xml.apache.org>
Sent: Tuesday, October 22, 2002 4:11 PM
Subject: Re: DO NOT REPLY [Bug 13845] - Axis logs/prints and exception when
it shouldn't
> (bugzilla down...)
Ok, I thought it was me, our network is playing up today. with 1 ping in 3
to my mailserver dropping out.
>
> Don't forget about our "enterprise" level logging. It's not clear to me
> that this particular situation applies.. but it's out there if it does.
We need to look at logging in general. I've just been tweaking the
AxisServlet so that when the development property is set
(axis.development.system) , then we do return a stack trace on invalid WSDL,
but even that isnt enough to help me track down why the WSDL is broken.
So in this case we need more diagnostics, not less.
The big issues we have with exceptions right now are
1. we dont distinguish between 'valid' exceptions from the invocation, and
unexpected faults, hence the bugrep.
2. the body of axis faults created by wrapping other exceptions, often
contains stack traces that we dont want to get out to the caller.
Really we need to
-keep stack trace info separate and private at production time
-distinguish endpoint originated exceptions from other exceptions, and not
log the endpoint ones
How can we go about doing this?
Re: DO NOT REPLY [Bug 13845] - Axis logs/prints and exception when it
shouldn't
Posted by Richard Sitze <rs...@us.ibm.com>.
(bugzilla down...)
Don't forget about our "enterprise" level logging. It's not clear to me
that this particular situation applies.. but it's out there if it does.
<ras>
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
bugzilla@apache.org
10/22/2002 01:46 PM
Please respond to axis-dev
To: axis-dev@xml.apache.org
cc:
Subject: DO NOT REPLY [Bug 13845] - Axis logs/prints
and exception when it shouldn't
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845
Axis logs/prints and exception when it shouldn't
------- Additional Comments From stevel@apache.org 2002-10-22 18:46
-------
We are going to have to distinguish genuine method raised faults from
unexpected
something-went-wrong with the invocation faults, then.
How do you propose we do this?