[
https://issues.apache.org/jira/browse/AXISCPP-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-100.
------------------------------
Resolution: Fixed
Fix Version/s: current (nightly)
OK, finally got this done. Tracing is now integrated in the code so that only
one binary is needed when we put out a release. I have also disabled and
removed the previous support in which a tool was used to dynamically produce
source with a trace points. That was kludgy and introduced complexity when
trying to do tracing of the xml parser and transport, and channels. It is much
cleaner now. Here is the information on the support.
To enable tracing, simply set one of ClientLogPath or LogPath (for server
logging) to the path of the trace file in the axiscpp.conf file. With this
support, a new configuration variable, LogFilter, can be set to filter the
trace records so you can isolate a component. The filter is a semicolon
delimited string of possible filters. Possible filters include:
* stub - show trace records generated
by stubs
* engine - show trace records generated by
engine
* parser - show trace records generated
by parser
* transport - show trace records generated by
transport
* noEntryExit - do not show entry/exit trace
records
The default filter is "stub;engine;parser;transport". So, for example, if I
wanted to enable client trace and show only transport trace records and no
entry/exit trace records, then the following would need to be specified:
> enable axis c++ (engine) tracing
> --------------------------------
>
> Key: AXISCPP-100
> URL: https://issues.apache.org/jira/browse/AXISCPP-100
> Project: Axis-C++
> Issue Type: Wish
> Components: Trace Utility
> Affects Versions: future (enh)
> Environment: ALL
> Reporter: Aleksander Slominski
> Fix For: current (nightly)
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
