axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Mon, 31 Jan 2005 01:59:17 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-100:

Nadir Amra :
This is something that is needed.  I realize there is a way to incorporate
tracing tool to do debugging, but I think we need something that is in the
code without a need to use the tool, and that is activated by a
configuration file switch.  It is on my todo list to use the trace class
(and enhance it) so that there is a global trace object that can be called
by all parts of axis.  This class will have methods to dump put entry/exit
and various other objects.

John also mentions ffdc, or maybe an eventlog, to write out serious errors
(on unix maybe it would go to syslog, etc.).  Another thing on my list.

Lots of work, but I will get this in, one way or another!

> enable axis c++ (engine) tracing
> --------------------------------
>          Key: AXISCPP-100
>          URL:
>      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:
If you want more information on JIRA, or have a bug to report see:

View raw message