axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Sat, 16 Oct 2004 01:06:51 GMT
The following comment has been added to this issue:

     Author: Aleksander Slominski
    Created: Fri, 15 Oct 2004 6:06 PM
i was looking for a way to control different levels of tracing/debugging messages for different
modules of AXIS so for example so i could see what happens when SOAP message is routed or
deserialized. seeing lot of enrty/exit procedure calls may be very difficult to grok ...

best if it can be enabled/disabled in running application - web admin interface to AXIS C++?

View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-100
    Summary: enable axis c++ (engine) tracing
       Type: Wish

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
             future (enh)

   Reporter: Aleksander Slominski

    Created: Thu, 17 Jun 2004 2:33 AM
    Updated: Fri, 15 Oct 2004 6:06 PM
Environment: ALL

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