1.0 Log and Trace Analyzer
1.1 Views
1.2 Importing Logs
1.2.1 Problems when importing remote log files
1.2.2 Importing log files on Linux and AIX
1.2.3 Importing WebSphere Application Server trace.log
1.2.4 Some log files cannot be imported using IBM Agent Controller V5
1.2.5 Out of memory exception
1.2.6 Index out of bounds error on adding log file in Import Log File wizard on Linux GTK driver
1.2.7 Common Base Events shown for DB2® Diagnostic log are not to specification
1.2.8 Errors Importing Log files not displayed
1.2.9 Limitation importing WebSphere activity.log files
1.2.10 Limitation importing log files generated in a different locale
1.2.11 Importing fails with InvocationTargetException message
1.2.12 NullPointerException when importing an empty log
1.3 Database support
1.4 Other
1.4.1 New Log Correlation wizard not displayed properly on Linux GTK driver
1.4.2 Modifications to a plug-in's logging level after the first start of the workbench are not respected
1.4.3 Problems unzipping with Windows XP unzip utility
1.4.4 Crash when creating an example on Red Hat Linux v8.0 with IBM JVM
1.4.5 Browser restriction for viewing Logging Utilities XML log files
1.4.6 Only TPTP format symptom databases can be created from the Log Navigator toolbar and popup menu
2.0 Profiling Tool
2.1 Agent and Process Interaction views are not supported from Sequence Diagram view
2.2 Refresh views command of the Profiling Navigator does not work for Trace Interactions
2.3 Profiling on Windows using the Sun JDK 1.4.x can end with a Microsoft® error report
Additional readme information associated with the TPTP Log and Trace Analyzer is available in the TPTP V3.3 release notes.
When importing a remote log file (File > Import... > Log File), no log entries are displayed in the Log View after refreshing the Profiling Monitor's Views (Profile > Refresh Views) or a Logging Message dialog is displayed stating that the local client has not started monitoring the remote log parser after waiting 30 seconds.
This problem is due to network latency and can be fixed by increasing the time the Agent Controller waits for the local client to start monitoring the remote log parser. To work around this problem, try the following steps:
<Application configuration="default" executable="RemoteLogParserLoader" extends="default" location="%SYS_TEMP_DIR%" path="%JAVA_PATH%"> ... <Parameter position="prepend" value="-Dorg.eclipse.hyades.logging.parsers.maxWaitTimeInMillis=xxxxx"/> ... </Application>where xxxxx is the maximum wait time in milliseconds (i.e. greater than 30000).
Some log file imports do not work at all on the Linux and AIX® platforms.
This occurs when the user does not have proper permissions to access the log files. To resolve this issue, the log files should be copied into the user's home directory and imported from there.
1.2.3 Importing WebSphere Application Server trace.logAn Internal Correlation is created when a WebSphere Application Server trace.log file is imported.
The user should not delete these correlations as they contain information related to the internal structure of the corresponding agent.
1.2.4 Some log files cannot be imported using IBM Agent Controller V5Remote log files other than activity.log cannot be imported using a V5 IBM Agent Controller. When importing log files remotely, the Agent Controller on the remote machine must be at the same level or higher as the Log and Trace Analyzer for Autonomic Computing.
To work around this limitation, install the IBM Agent Controller shipped with the Log and Trace Analyzer on the remote machine.
1.2.5 Out of memory exceptionLog files up to 25MB can be imported into the workspace and opened into the Log and Trace Analyzer. The amount of time to open the log file depends on the number of log records in the file and you may get an "out of memory" exception.
To work around this problem, use the large log support feature.
1.2.6 Index out of bounds error on adding log file in Import Log File wizard on Linux GTK driverDuring the import of a log file, Index out of bounds error is raised when you try to click OK in the Add log file wizard. This is due to the fact that the log file being added does not have a version selected.
Make sure a valid version option is selected in the version pull-down list under the Detail tab of the Add Log File wizard.
If you import a DB2 Diagnositic log, the resulting Common Base Events shown in Log and Trace Analyzer breaks some of the Common Base Events specification. This is due to a bug in the db2diag.exe utility which is used to convert DB2 Diagnostic logs to Common Base Events. This should not affect operation. There is no known work-around until db2diag.exe is fixed.
No validation is done by Log and Trace Analyzer on the type of log file being imported. When importing a log file ensure that the correct log type and version is chosen for the log file that is being imported. If a problem occurs during the import, no records or incorrect records are shown in the Log View and an error message will be displayed. For more detailed information about the error, view the details from the error dialog or try looking in the file .metadata\.plugins\org.eclipse.hyades.logging.adapter\hgla.log, if it exists in the workspace directory. This file may contain information on errors that occurred during the parsing of the log file.
If an error occurs importing a log file an error message is displayed and no records are shown in the Log View or incorrect data is shown in the records in the Log View.
When importing WebSphere Application Server activity log files from or on non-English machines, the rules-based log file parser does not successfully map log record data to a Common Base Event. Instead, some log record data may appear in the incorrect field of the Common Base Event.
To work around this problem, when importing WebSphere Application Server activity log files from or on non-English machines, use the static log file parser.
When importing log files that contain timestamps in a locale different than the locale that Log and Trace Analyzer is executing in, the rules-based log file parser sometimes does not parse the timestamp and other log record data correctly. For example, when importing an English IBM HTTP Server access log file into the Log and Trace Analyzer running on a Japanese machine, the creationTime values in the resulting Common Base Events will have a value of zero and the Common Base Event msg field will be blank.
To work around this problem, when importing log files containing timestamps in a different locale than the current machine locale, use a static log file parser, if available.
If Log and Trace Analyzer has not be installed correctly and some of its files are missing, importing a log file may fail with the following logging message:
java.lang.reflect.InvocationTargetException
To work around this problem, reinstall Log and Trace Analyzer. Note: When installing on Windows XP, do not use the native Windows XP unzip utility. See Problems unzipping with Windows XP unzip utility, below, for more details.
When an empty log is imported or when an import filter is used that filters out all log events, the Log View will appear empty and a NullPointerException (in XMLLoader.endElement) may be thrown. Check the log file or try a different filter which will allow some events to be loaded.
N/A
In the New Log Correlation wizard, only the Available Logs list is shown, and the list is empty. This is due to the fact that only the left portion of the wizard page is displayed.
To work around this problem, try resizing the wizard page to have the Selected Logs list and actions buttons shown. An alternate workaround is to select the log files for correlation in the Log Navigator view before clicking the New Log Correlation button.
If you modify a plug-in's logging level in its plugin.xml file (via the com.ibm.etools.common.logging.commonLoggingOptions or com.ibm.etools.logging.util.loggingOptions extension points) after the first start of a workbench, the change is not respected in subsequent launches of the workbench. The logging level specified in the plug-in's plugin.xml file is cached by the Eclipse run-time on the first start of the workbench. Subsequent starts of the workbench use the cached value of the plug-in's logging level despite modification in the plugin.xml file.
To work around this problem, restart the workbench with the -clean command line argument. This option will clean the caches used to store bundle dependency resolution and eclipse extension registry data and force Eclipse to reinitialize these caches. Add the option after the eclipse.exe in the <workbench installation directory>\eclipse\ac.bat (Windows) or <workbench installation directory>/eclipse/ac.sh (Linux). Alternatively, you can modify the plug-in's logging level on the Logging preferences page (Window > Preferences > Logging) and restart the workbench.
When installing Log and Trace Analyzer on Windows XP, there are problems unzipping the Log and Trace Analyzer runtime file with the Windows XP native unzip utility. Some directories and files are not unzipped. As a result of this problem, some log file types cannot be imported using Log and Trace Analyzer.
To work around this problem, when installing on Windows XP, use another unzip utility such as WinZip or UnZip.
When creating an example in the Log and Trace Analyzer using the Example Creation wizard (New > Example), the Workbench crashes. This happens when the Example Creation wizard tries to open the readme.html file as part of the creation steps. This problem is found on Red Hat Linux v8.0 with the IBM JVM, and is an SWT bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=76515).
To work around this problem, try adding -Xj9 as a JVM argument in ac.sh to launch using the IBM J9 JVM. (for example, ./eclipse -vmargs -Xj9 -Xmx500m). For more information about running SWT on Red Hat Linux v8.0, check the SWT FAQ (http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/faq.html).
Note: As stated on Eclipse reference platforms table (http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_0.html#TargetOperatingEnvironments), only the following Linux systems are supported: version 2.2.1 of the GTK+ widget toolkit and associated librares (GLib, Pango); SWT HTML viewer requires Mozilla 1.4GTK2. For Motif on other Linux systems: Open Motif 2.1 (included); SWT HTML viewer requires Mozilla 1.4GTK2.
The CommonBaseEvents.log file generated by the workbench is best viewed using the Log views provided by the Logging tools. Alternatively, you can use an XML-enabled browser to view the XML document format of the log file (that is, the file called CommonBaseEvents.log_Viewer.xml in the workspace\.metadata subdirectory of the installation directory). This file can only be viewed using Microsoft Internet Explorer V6.0.28 and above.
Because of a TPTP limitation users cannot create both types of symptom databases from the log navigator toolbar button and context menu. A workaround is to select File > New > Other > Profiling and Logging from the workbench menu and choose the type of symptom database you want to create.
The Agent Interactions view and the Process Interactions view are not supported from the Sequence Diagram view for log files.
There is currently no workaround for this problem.
2.2 Refresh views command of the Profiling Navigator does not work for Trace InteractionsRefresh views command of the Profiling Navigator does not work for Trace Interactions. However, the trace interactions automatically refresh on their own at regular intervals.
A workaround is to select another node in the Profiling tree and select again the previous node.
2.3 Profiling on Windows using the Sun JDK 1.4.x can end with a Microsoft error reportBugzilla defect: 103058
The profiling or application terminates with the message "java.exe has encountered a problem and needs to close. We are sorry for the inconvenience.". The message contains information and choices for submitting an error report to Microsoft. See bugzilla 103058 for a screen capture of the message.
This problem has been observed in a number of modes: Time Analysis (with or without "Show Instances"), Memory Analysis, and in combinations of these modes. You can work around the problem by re-running the profiling or appliaction with JIT turned off, i.e. by supplying "-Djava.compiler=NONE" as a JVM argument. The problem has been encountered with the SUN JDK 1.4.2_08-b03 build for Windows.
Return to the main readme file
© Copyright IBM Corporation 2000, 2005. All Rights Reserved.