axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Mon, 31 Jan 2005 10:47:19 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-100?page=comments#action_58297 ]
     
Mark Whitlock commented on AXISCPP-100:
---------------------------------------

Currently there is entry/exit/catch trace in almost all methods (added in by the TraceInstrumentor
at ant build time). Catch trace is trace automatically added into catch blocks. There are
a few files that trace is not added into. These are listed in ws-axis/c/tools/org/apache/axis/tools/trace/tracetool.conf.
They include files such as AxisTrace.cpp which should never be instrumented with trace, and
other files which the tool fails to parse. The files that the tool fails on are mostly not
used by Axis.

I hope people find the trace useful and readable. For instance methods, "this" is output in
< >, so you can see which instance a method is being called for. In methods that contain
multiple return statements or multiple catch blocks, which return or catch is shown after
an @ sign.

Here are some enhancements I hope to add to the trace support...
 - Support the free trace viewer from alphaworks (see not from John above).
 - Output large data areas properly (only the first 32 bytes are output at present)
 - Trace pointers to primitives better
 - Startup trace - tracing before axiscpp.conf is read in
 - Trace thread ids
 - Throw trace - instrument the code to add in trace around a throw statement.
 - Trace catch (...) blocks better so I can see what has really been caught.
 - I suspect trace may get the length of derived classes wrong so not all the data is output.
 - Component trace - so that only certain components are traced.
 - Trace enums better - so AXIS_SUCCESS comes out as AXIS_SUCCESS and not 0.
 - Server-side trace

I haven't added in component trace up until now because the client side trace is not so massive
that it is difficult to read. Also the trace viewer will enable component filtering.


> 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