You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/15 12:55:51 UTC

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

The following comment has been added to this issue:

     Author: John Hawkins
    Created: Fri, 15 Oct 2004 3:55 AM
       Body:
We ahve now have entry and exit trace. I suggest that this is the first step. Is this request for something more specific?
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-100?page=comments#action_54168

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-100

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++
   Versions:
             future (enh)

   Assignee: 
   Reporter: Aleksander Slominski

    Created: Thu, 17 Jun 2004 2:33 AM
    Updated: Fri, 15 Oct 2004 3:55 AM
Environment: ALL

Description:
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.



---------------------------------------------------------------------
JIRA INFORMATION:
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