1.0 Log and Trace Analyzer
1.1 Views
1.1.1 Log Navigator View does not refresh
properly
1.1.2 Advanced Filter does not filter log
records without matching attribute values
1.1.3 Profiling and Logging
perspective
may be missing toolbar buttons and menu items
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 Importing and viewing trace files
1.2.5 Agent Controller Security feature
not supported in the Log and Trace Analyzer
1.2.6 Some log files cannot be imported
using IBM Agent Controller V5
1.2.7 Out of memory exception
1.2.8 Index out of bounds error on adding
log file in Import Log File wizard on Linux GTK driver
1.2.9 Cannot import LoggingUtil.log file
from .metadata folder on Linux GTK driver
1.2.10 Cannot import log files requiring
conversion using rules-based parsers
1.2.11 Continuous monitoring of log
files with static parsers is not supported
1.2.12 Errors importing log files not
displayed
1.2.13 Limitation importing WebSphere
Application Server activity.log files
1.2.14 Limitation importing log files
generated in a different locale
1.2.15 Importing fails with
InvocationTargetException message
1.3 Other
1.3.1 New Log Correlation wizard not
displayed properly on Linux GTK driver
1.3.2 Modifications to a plug-in's
logging level after the first start of the workbench are not respected
1.3.3 Problems unzipping with Windows XP
unzip utility
1.3.4 Crash when creating an example on
Red Hat Linux v8.0 with IBM JVM
2.0 Profiling Tool
2.1 Agent and Process Interaction views are
not supported from Sequence Diagram view
2.2 Sequence Diagram view displays
misaligned return calls
2.3 Refresh views command of the Profiling
Navigator does not work for Trace Interactions
2.4 Profile on Server profiling options do
not apply to J2FF Request profiler
2.5 *New Filter Set creates filter rules in
English on
Non-English workbench, and English filter rules are treated as INCLUDE
when save
The Log Navigator view is not refreshed when a deletion is made in the Resource Navigator view.
The refresh can be done manually by right-clicking the Log Navigator view and selecting Refresh from Local in the context menu.
1.1.2 Advanced Filter does not filter log records without matching attribute valuesWhen using the Advanced Filtering in the Log View, log records without matching attribute values for the field specified in the advance filter table for comparison will not be filtered out.
There is currently no workaround.
1.1.3 Profiling and Logging perspective may be missing toolbar buttons and menu itemsIf you have previously profiled a Java application or any other launch configuration type, the Profiling and Logging perspective may have been opened without completely activating the Profiling and Logging capability. As a result, when you return to the Profiling and Logging perspective, most of the toolbar buttons and menu items will not be present.
To reveal the missing toolbar buttons and menu items:
To avoid this problem entirely, enable the Profiling and Logging capability before profiling anything.
When importing a remote log file (i.e. File > Import... > Log File), no log entries are displayed in the Log View after refreshing the Profiling Monitor's Views (i.e. Profile >b> 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"where xxxxx is the maximum wait time in milliseconds (i.e. greater than 30000).
location="%JAVA_PATH%" path="%JAVA_PATH%\java.exe">
...
<Parameter position="prepend"
value="-Dorg.eclipse.hyades.logging.parsers.maxWaitTimeInMillis=xxxxx">
</Parameter>
...
</Application>
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 Importing and viewing trace filesWebSphere Application Server V5.0.1 or lower trace files generated using the Log Analyzer trace output format cannot be imported and viewed using the Log and Trace Analyzer.
To work around this limitation, set the WebSphere Application Server trace output format to either Basic or Advanced before you generate trace files that are to be imported and viewed using the Log and Trace Analyzer.
1.2.5 Agent Controller Security feature not supported in the Log and Trace AnalyzerYou will not be able to profile an application or import a log file if you have installed the Agent Controller with security enabled
To work around this limitation, reinstall the Agent Controller with security disabled.
1.2.6 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.7 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, edit ac.bat or ac.sh and increase the memory by increasing the value of the "-Xmx" option from "500" to a higher value, such as "1000M" (startup will be slower with the increase) or add more physical memory to the machine. Alternatively, use the Large Log Support feature of the Log and Trace Analyzer.
1.2.8 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.
1.2.9 Cannot import LoggingUtil.log file from .metadata folder on Linux GTK driverLoggingUtil.log file in the .metadata folder of any workspace directory cannot be imported as the file selection dialog in import log wizard does not display .metadata folder
To work around this problem, copy the LoggingUtil.log file from .metadata folder to other visible folder directory.
1.2.10 Cannot import log files requiring conversion using rules-based parsersLog files that require conversion from a native format into a textual format cannot be imported (via File > Import > Log File) using the corresponding rules-based parser. The following log files are affected:
To work around this limitation, use the corresponding static-based parser, if one exists.
1.2.11 Continuous monitoring of log files with static parsers is not supportedYou cannot monitor log files continuously with static Java parser classes. Use the rules-based parser, if one exists, to continuously monitor these log files.
1.2.12 Errors Importing Log files not displayedIf an error occurs importing a log file sometimes an error message is not displayed and no records are shown in the Log View or incorrect data is shown in the records in the Log View. Ensure that the correct log type and version is chosen for the log file that is being imported. No validation is done by Log and Trace Analyzer on the type of log file being imported.
1.2.13 Limitation importing WebSphere Application Server activity.log filesWhen 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.
1.2.14 Limitation importing log files generated in a different localeWhen 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.
1.2.15 Importing fails with InvocationTargetException messageIf 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.
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.
1.3.2 Modifications to a plug-in's logging level after the first start of the workbench are not respectedIf 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, delete the <workbench installation directory>\configuration directory and restart the workbench. Alternatively, you can modify the plug-in's logging level on the Logging preferences page (Window > Preferences > Logging) and restart the workbench.
1.3.3 Problems unzipping with Windows XP unzip utilityWhen 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.
1.3.4 Crash when creating an example on Red Hat Linux v8.0 with IBM JVMWhen 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 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 Sequence Diagram view displays misaligned return callsThe Sequence Diagram view may display misaligned return calls which point to white space instead of a method node.
There is currently no workaround for this problem.
2.3 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.
A workaround is to select another node in the Profiling tree and select again the previous node.
2.4 Profile on Server profiling options do not apply to J2FF Request profilerProfile on Server Attach wizard allows you to configure profiling options (for example, profiling set or profile filter). These profiling options do not apply to any J2EE Request profiler selected to attach. The profile options are only applicable to the PiAgent Profiler.
*2.5 New Filter Set creates filter rules in English on Non-English workbench, and English filter rules are treated as INCLUDE when saveWhen creating a new filter set on a non-english workbench. The new filter targets initially come up in English. Furthermore, filter rules that are in English are ignored and always treated as INCLUDE when save.
A workaround is to profiling using packaged filter set and modify(add/remove) their filters for profiling, or save the new filter set by Apply and Close the launch wizard, then reopen and modify them before profile.
Note: This has been fixed in V6.0.0.1.
Return to the main readme file