axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Hawkins (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Thu, 27 Jan 2005 13:52:18 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-100?page=comments#action_58151 ]
     
John Hawkins commented on AXISCPP-100:
--------------------------------------

We have the trace tooling which adds in entry and exit trace to MOST methods on-the-fly in
the build process (ANT build only) (using an AOSD approach where we parse the file looking
for entry and exit points). I looked into using C OASD and frankly it wasn't up to the job
(July 2004). I got the impression that we'd struggle to compile it on many platforms as well.

We have found this extremely useful in debugging problems.  It puts out what methods you are
entering and exiting from but also parameter details. If an AxisException is  thrown then
a lot of information goes into the log too. Thread info is also put out (or will be soon!)

By default this trace is off and needs a compile time flag to turn it on.


The trace is being output (as of tomorrow) in an IBM format that can be viewed with a free
viewer from alphaworks http://alphaworks.ibm.com/tech/ta4was However, it is also fairly easy
to read by a human without the reader.

However, having said all that. I would like to also do  what is called FFDC (First Failure
Data Capture) which means that when we catch an exception we output a file for later diagnostics.
The advantage being that you don't have to ask the user to rerun with trace on as you should
have lots of information in the output file.


Having said all that. This defect was to do with general trace and not necessarily entry and
exit. We already have this API in the code it's just that it is not used much :-)

I would like to move to a more well known Opensource trace package (LOG4C) in a future release
as most of what we have written is bespoke. ICU4C is based on a well known trace package LOG4J
which has the requested trace levels in this issue. But, as there is so little trace in the
code, I don't see the point in worrying too much about levels at this point.

> enable axis c++ (engine) tracing
> --------------------------------
>
>          Key: AXISCPP-100
>          URL: http://issues.apache.org/jira/browse/AXISCPP-100
>      Project: Axis-C++
>         Type: Wish
>     Versions: future (enh)
>  Environment: ALL
>     Reporter: Aleksander Slominski

>
> i think it would be good to have some kind of tracing/logging compiled into binary that
could be triggered by setting environment variable (for example AXISCPP_TRACE=engine:ALL).
> it would be very useful tool when debugging such problems like wrong SOAPAction to see
if engine received request and see where did it go and why it was rejected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message