© Copyright International Business Machines Corporation 2000, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
In the Log View, the Filtering and Highlighting functions do not work on complex elements of the Log event (for example, sourceComponentId)
When importing a remote log file (File > Import > Profiling and Logging > 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 Agent Controller waits for the local client to start monitoring the remote log parser. To work around this problem, try the following steps:
Try to import the log file again.
If the symptoms persist, add the following entry to the remote RemoteLogParserLoader application in Agent controller's configuration (i.e. <Agent Controller's installation directory>/plugins/com.ibm.etools.logging.parsers/config/pluginconfig.xml):Once the update is made, restart Agent Controller and try importing the log file again.<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.
An 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.
Log files up to 25MB can be imported into the workspace. 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.
If you import an IBM DB2® Express Diagnostic log, the resulting Log events shown do not completely follow the Log event specification. This is due to a bug in the db2diag.exe utility which is used to convert DB2 Diagnostic logs to Log events. This should not otherwise affect the import operation. There is no known workaround until db2diag.exe is fixed.
No validation is done 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.
When importing log files that contain timestamps in a locale different than the locale that the workbench 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 to a Japanese machine, the creationTime values in the resulting Log events will have a value of zero and the Log 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, specify the locale of the log file on the Details tab in the Log Import wizard, if a locale field exists.
Importing a binary WAS Activity log with the Rules parser from an AIX system fails with the following error displayed in the error dialog:
IWAT0030E An error occurred during the execution of the remote log
parser "com.ibm.etools.logging.adapter.config.StaticParserExtension":IWAT0412E Errors occurred parsing the log file /home/tfoun/logs/activity.log.
java.lang.Exception: IWAT0239E Converter command failed: java.lang.Exception:
IWAT0238E Converter process ended with exit value 1The converter command to convert the binary log file to text so that it can be parsed fails on AIX. To work around this problem, either use the Static parser to import the binary activity log file or convert the binary activity log file to text using the WAS showlog utility and import the resulting text file. The WAS showlog utility can be found in the bin directory in the WAS installation directory. For example, use the following command to convert the binary log file to a text file called activity.txt:
/opt/WebSphere/AppServer/bin/showlog activity.log activity.txt
Then, import activity.txt.
When specifying log files to import, you can create advanced filters. In the Add Filter Property dialog box, there is a combo box for the Attribute field. This combo box lists a number of the Log event properties. Note it does not list the complex types for the Log event properties.
When importing multiple log files simultaneously, the dates on the imported records may be incorrect. To work around this problem, import the files one at a time.
Concurrent client access to a database might lock some tables. To unlock the tables, restart the Workbench and the database server.
If you use the same database and database account for multiple workspaces, resource path collisions may result and resource will not be persisted into the database.
To work around this problem, use different project and monitor names in each workspace to avoid resource path collisions.
In Linux/GTK, on the Large Resource Support preferences page, the database settings fields will remain disabled even when a valid database type is selected.
To work around this problem, select DB2 as the database type, and apply the settings. Close and reopen the preferences dialog; the fields will be enabled.
To improve the performance of large log support, run the following command after you have imported large logs:
db2 -tvf plugins/com.ibm.etools.ac.resources.database_x_x_x /scripts/runStatsForAllHyadesTablesDB2-8.1.sql
where x_x_x is the version number on the plug-in directory.
Occasionally, the following SQL exception may occur:
com.ibm.db2.jcc.b.SQLException: NULLID.SYSSH203 0X5359534C564C3031
When this problem occurs, restart the workbench and the database, if using DB2 or Cloudscape™ in network mode. Logs imported when this exception occurs will not be valid and will have to be re-imported.
In the Large Log Support page of the Profiling and Logging section of the Preferences dialog, if you click Test connection before you have applied changes to settings, you may get a connection error. To avoid this, click Apply after making any setting changes and then click Test connection.
The following XPath expression is not supported when analyzing large logs.
<expression:xpathExpression>/CommonBaseEvent</expression:xpathExpression>
If DB2 is used for large log support, only one contextDataElement for an event is displayed in the Log view, even if there are multiple contextDataElements for that event.
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.
When creating an example 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 Java™ Virtual Machine (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.
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.
In XPath rules and IBM correlation rules, the string in the msg Log event property should not be more than 1024 bytes. If the string is more than 1024 bytes, they will not be processed.
When using complex elements of the Log event (for example, sourceComponentID), Symptom Editor generates XPATH rules that are not valid.
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.
Refresh 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.