axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Hawkins <>
Subject Re: [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Thu, 27 Jan 2005 17:16:54 GMT
Hi Nadir,

Tracing is configurable currently, if you do not set the CLIENTLOGPATH  in 
the axiscpp then you do not get *any* trace.  However, for a server this 
would be no good :-)

John Hawkins

Nadir Amra <> 
27/01/2005 17:01
Please respond to
"Apache AXIS C Developers List"

"Apache AXIS C Developers List" <>

Re: [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing

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!

Nadir K. Amra
e-Business Technologies - IBM eServer i5/OS
IBM Rochester, MN,  (Tel. 507-253-0645, t/l 553-0645)

"Samisa Abeysinghe (JIRA)" <> wrote on 01/27/2005 
07:08:17 AM:

>      [
> page=comments#action_58150 ]
> Samisa Abeysinghe commented on AXISCPP-100:
> -------------------------------------------
> Are we happy with the current level of tracing available with Axis C++?
> Do we have any plans to implement the said level of tracing? 
> Do we have this kind of feature with Axis Java?
> Personally I do feel that this level of tracing would help; however 
> would make the code too clumsy, unless otherwise we use AOP, which 
> is far too much. Hence I do not think we should go for this.
> > 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.

View raw message