axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-406) Make AxisTrace work better with TraceAnalyzer
Date Mon, 28 Feb 2005 16:21:48 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-406?page=comments#action_59863 ]
     
Mark Whitlock commented on AXISCPP-406:
---------------------------------------

I discussed these problems with the originators of the trace analyzer tool.

 - Object ids can be searched on by the tool, but the use of a vertical bar | to distinguish
object ids is unfortunate since that is used as an OR sign by the tool.

 - They will fix the environment data limit

 - They will provide a "throw out" trace type so that trace statements that throw an exception
back out to the application will cause the stack to unwind as shown by the tool.

 - The tool shows the first line of a multiline trace statement in the trace window and subsequent
lines are shown in the detail window. So I should output a parameter summary in the first
line of each trace statement, and a fuller output in subsequent lines. This could also be
done where the trace needs to dump a large amount of data.

> Make AxisTrace work better with TraceAnalyzer
> ---------------------------------------------
>
>          Key: AXISCPP-406
>          URL: http://issues.apache.org/jira/browse/AXISCPP-406
>      Project: Axis-C++
>         Type: Bug
>   Components: Trace Utility
>     Versions: 1.5 Alpha
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock
>     Priority: Minor

>
> I have formatted axis trace so that it is compatible with the free trace analyzer available
from http://alphaworks.ibm.com/tech/ta4was. However there are some unresolved issues. There
are....
>  - the timestamp on every line does not include milliseconds because struct tm does not
support milliseconds. This might require platform specific functions. Timestamps without milliseconds
don't make much sense since many calls happen in every second.
>  - the environment variable section at the top of the trace easily blew the tool's limit.
When there was too much data in that section, the tool failed to read in the trace file.
>  - The thread id is not output in the trace because the client library is not currently
linked with pthreads (it should be).
>  - Character strings that contain newline characters are split over several lines in
the trace. This is OK, but it looks a little odd. I can't think of a better solution.
>  - Object ids (value of the this pointer) appears in the trace, but are they output so
that the tool can show all methods acting on a particular instance of a particular class.

-- 
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


Mime
View raw message