Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <526729367.1107427039030.JavaMail.jira@ajax.apache.org>
Date: Thu, 3 Feb 2005 11:37:19 +0100 (CET)
From: "Mark Whitlock (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Created: (AXISCPP-406) Make AxisTrace work better with
 TraceAnalyzer
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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
 Assigned to: 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