Release notes
Release notes for TPTP V4 (all releases)
General Notices
1.0 Known problems and limitations
1.1 Generic Log Adapter
1.1.1 Problems running Generic Log Adapter rules IBM's Java Runtime Environment (JRE) v1.4.1
1.1.2 Importing a log file from a remote z/OS system may result in incomplete data
1.1.3 Generic Log Adapter does not support creating rules to parse multiple timestamp formats
1.1.4 Formatter errors in Problems view when new Generic Log Adapter adapter file is run in the Generic Log Adapter perspective
1.1.5 Generic Log Adapter Documentation Error - Configuring the parser component for a rules based adapter
1.1.6 Not all Generic Log Adapter messages are displayed in the Problems view when running an adapter file in the Generic Log Adapter perspective
1.1.7 Executing standalone Generic Log Adapter with the Language Pack requires jars to be added to the class path
1.1.8 HTTP Server access log rules parser does not parse some records correctly
1.2 Agent Controller
1.2.1 Console text is garbled when profiling a Java application on a DBCS system
1.2.2 Agent Controller file copy on HP 11i does not work
1.2.3 Agent Controller reports "sh: sysdef: not found" error on Solaris
1.2.4 Agent Controller running with a Sun JVM on Linux enters an infinite loop
1.2.5 Multiple instances of Agent Controller on one machine not permitted
1.2.6 FileNotFoundExceptions not reported by file transfer engine when files on remote server cannot be found
1.2.7 Running the Agent Controller under secured mode on iSeries
1.2.8 Data not collected when monitoring multiple agents simultaneously
1.2.9 Data bytes are lost when profiling data is transferred through a Zone Labs firewall
1.2.10 "Out Of Memory" error when profiling applications
1.2.11 Data collected by agent does not reach the client
1.2.12 Unsuccessful termination of an agent that is running in a process with multiple agents
1.2.13 Agent Controller crashes if an agent is run in "headless" mode and the logFile attribute is not specified
1.2.14 An error message is not generated when an invalid path to java.exe is specified in serviceconfig.xml
1.2.15 An error message is not generated when an invalid path to java.exe is specified in serviceconfig.xml
1.2.16 Multithread capability has to be enabled when running an agent under OS/400 (iSeries)
1.3 Log and Trace Analyzer
1.3.1 Continuous log monitoring is not supported for localhost
1.3.2 Logging examples readme file does not open
1.3.3 Simultaneous clients access using the same database account is not supported
1.3.4 Resource path collision
1.3.5 Large Resource Support preferences remain disabled despite valid selection
1.3.6 Improving performance of large log support
1.3.7 Restart DB2 after creating database and tables
1.3.8 Intermittent SQL exception
1.3.9 Importing a log from an IBM iSeries system causes a timeout error message
1.3.10 Remote Log Import from HP-UX system with a filter causes a NullPointerException error message
1.3.11 Remote Log Import with a filter does not work when Agent Controller is started incorrectly
1.3.12 Unreadable data in some events when importing Microsoft Windows System event log on DBCS system
1.3.13 Importing Windows Application event log generates Common Base Event formatting errors
1.3.14 Importing Windows event log with a filter fails
1.3.15 Importing a log file from a remote z/OS system may result in incomplete data
1.4 Probekit
1.4.1 Probekit may fail to instrument certain large Java methods
1.5 Profiling Tool
1.5.1 Problem with garbage collection when using IBM JDK 1.4.1
1.5.2 With Sun JVM, some method calls are not traced
1.5.3 Profiling on Solaris using the Sun JDK 1.4.x or on HP using the HP JDK 1.4.x may cause JVM to crash
1.5.4 Potential crash when running in standalone mode with STACK_INFORMATION=contiguous on Solaris
1.5.5 Negative timeout values for WAIT and WAITED events
1.5.6 Incorrect monitor dumps with IBM JDK 1.4.2
1.5.7 Method counts incorrect with JIT Inlining
1.5.8 Method level CPU time statistics limitations on AIX and Solaris
1.5.9 Profiling to an existing profile file fails on Linux
1.5.10 Importing profile files generated from headless profiling
1.5.11 Import profile file with package level filtering shows empty view
1.5.12 Profiling mode shows more data than expected
1.5.13 Free Up Memory action saves only selected resources in the Profiling Monitor view
1.5.14 "Execution History - Full Graphical Details" profiling set involves collection of boundary classes
1.6 Statistical Console
1.7 Test
1.7.1 Common Test Issues
1.7.1.1 National characters are currently not supported in creating test suites and test cases
1.7.2 URL Test
1.8 Charting Service
1.8.1 SVG filter effects are not supported in Mozilla native SVG browsers
1.8.2 The Adobe SVG v3.0 plug-in is required to view test reports in Internet Explorer
1.8.3 Hungarian is not supported by SVG Adobe Viewer 3.0

General Notices

References to "Hyades" should be read as equivalent to "TPTP".

Any references to "Hyades" in the documentation, installation, migration, or readme files should be read as equivalent to "Test and Performance Tools Platform", or "TPTP".

1.0 Known problems and limitations

1.1 Generic Log Adapter

1.1.1 Problems running Generic Log Adapter rules using IBM's Java Runtime Environment (JRE) v1.4.1

The IBM JDK 1.4.1 that ships in 2003 causes problems in the rule-based Apache access log parser.

Service Release (SR2) and above is required when running IBM's Java Runtime Environment (JRE) v1.4.1 to use the Generic Log Adapter and/or importing log files using a rules-based log file parser.

1.1.2 Importing a log file from a remote z/OS system may result in incomplete data

Bugzilla defect: 80730

Parsing a log file using Generic Log Adapter on a z/OS system may result in incomplete data. The parsing operation may stop prematurely and not all of the log records are parsed. This problem occurs when one of the following IBM JDK versions is installed on the z/OS system:

1.4.1 PTF UQ88783
1.4.2 PTF UQ90449
1.4.2 PTF UQ93743 

This problem is fixed in IBM JDK 1.4.2 with PTF UK00802. Upgrade the JDK to that version or a later version. If you cannot upgrade the JDK version, execute Generic Log Adapter with the Java JIT compiler disabled to work around the problem. To disable the Java JIT compiler, add the following JVM argument to the java command in the script file used to execute Generic Log Adapter:

-Djava.compiler=NONE

1.1.3 Generic Log Adapter does not support creating rules to parse multiple timestamp formats

Generic Log Adapter does not support parsing log files that have locale sensitive timestamp formats with a single rules-based adapter configuration file. If an application generates log files containing timestamps that have formats dependant on the locale it is generated in, then these logs cannot be parsed with a single rules-based adapter. For example, if the date format is MM/dd/yy in log files generated on en_US systems, yy/MM/dd in log files generated on ja_JP systems, and dd.MM.yy for log files generated on de_DE systems then a separate adapter configuration file is required to parse each log file, each one having a parsing rule with the correct timestamp format for the locale.

1.1.4 Formatter errors in Problems view when new Generic Log Adapter adapter file is run in the Generic Log Adapter perspective

Bugzilla defect: 62103

The Problems view in the Generic Log Adapter perspective returns the following error when trying to execute a new Generic Log Adapter adapter file by clicking the Rerun adapter ..." button:

IWAT0438E Common Base Event formatter N76D20B0042411D98000E0362B33D6F0 cannot 
create a CommmonBaseEvent because required property sourceComponentId is 
missing.

This message indicates that the formatter component of Generic Log Adapter could not create a Common Base Event because sourceComponentId is a required property of Common Base Event and it is missing. To work around this problem, add parser rules to the adapter file for the sourceComponentId attributes. Note that the situation property is also a required Common Base Event property. To avoid similar errors, add parser rules to the adapter for the situation property. Generic Log Adapter will only create CommonBaseEvents that contain all of the required properties.

1.1.5 Generic Log Adapter Documentation Error - Configuring the parser component for a rules based adapter

Bugzilla defect: 96660

In the online help for the Generic Log Adapter, information in the following help file is incorrect: Generic Log Adapter -> Creating a log parser -> Create a rules-based adapter -> Configuring the parser component. In Step 3 under "Adding and configuring attribute substitution rules", the sentence, "if you just want to assign the value of the warning to the Common Base Event msg attribute, specify the substitution as $2.", should state "if you want to assign the part of the message after the dash to the Common Base Event msg attribute, specify the substitution as $2."

1.1.6 Not all Generic Log Adapter messages are displayed in the Problems view when running an adapter file in the Generic Log Adapter perspective

Bugzilla defect: 101367

Sometimes when the Generic Log Adapter configuration file is incorrect and it is executed in the Generic Log Adapter perspective by clicking the Rerun adapter ... button, not all of the error messages are shown in the Problems tab view. The number of errors indicated at the top of the Problems tab is correct but less than that number are shown in the Problems table. To work around this problem click the Filters... button on the Problems tab tool bar and click OK in the Filters dialog window that is displayed. The table in the Problems tab view will be refreshed with all of the error messages.

1.1.7 Executing standalone Generic Log Adapter with the Language Pack requires jars to be added to the class path

To use the Generic Log Adapter Language Pack, unzip it in the same directory or folder where you unzipped the Generic Log Adapter standalone run-time. Also, the following jar files need to be added to the class path when executing the Generic Log Adapter:

INSTALLDIR\GenericLogAdapter\lib\org.eclipse.hyades.logging.adapter.nl1.jar
INSTALLDIR\GenericLogAdapter\lib\org.eclipse.hyades.logging.core.nl1.jar
INSTALLDIR\GenericLogAdapter\lib\org.eclipse.hyades.logging.parsers.nl1.jar

where INSTALLDIR is the directory or folder where you unzipped the Generic Log Adapter standalone run-time and language pack zip files. These jar files must be added to the class path in any script file used to execute Generic Log Adapter.

1.1.8 HTTP Server access log rules parser does not parse some records correctly

Bugzilla defect: 101545

HTTP Server access log rules parser does not parse the following records correctly:

9.26.5.6 - - [09/Feb/2005:17:07:53 -0500] "VERSION" 501 -
9.26.5.6 - - [09/Feb/2005:17:14:52 -0500] "GET_CONFIG\r" 501 -
9.26.5.6 - - [09/Feb/2005:17:15:00 -0500] "< NSP/0.2 >" 400 299
9.26.5.6 - - [09/Feb/2005:17:22:40 -0500] "\x16\x03\x01" 501 -

The severity is not parsed correctly for the first two records and the last record. Some of the other record data is not captured in extended data elements correctly.

1.2 Agent Controller

1.2.1 Console text is garbled when profiling a Java application on a DBCS system

When profiling a remote Java application within Eclipse on a DBCS (e.g. Traditional Chinese, Simplified Chinese, Japanese, Korean) system, the console output is displayed as garbled text. This problem may happen on any platform.

To work around this problem, add a Java VM argument -Dconsole.encoding=<native encoding> when launching the remote Java application. This will ensure proper encoding when transferring the console output from the remote side back to the Eclipse workbench. To determine <native encoding> on Windows, open a command prompt and run the command chcp. For example, if you get a result of 950 then the value of <native encoding> is MS950. The Java VM argument will then be -Dconsole.encoding=MS950. For a list of valid encoding, please refer to Sun's Java documentation, "Supported Encodings", under the section "Internationalization".

1.2.2 Agent Controller file copy does not work on HP 11i

The file copy does not work because the file server does not startup. This is due to the JVM library libjvm.sl not being loaded at run-time, which in turn causes the file server not to run.

To work around this, the linker patch version PHSS_30049 or higher is required. The linker version from patch 30049 is as follows:

/bin/ld:
     $Revision: 1.22 $
     HP aC++ B3910B X.03.37.01 Classic Iostream Library
     HP aC++ B3910B X.03.37.01 Language Support Library
     ld_msgs.cat: $Revision: 1.22 $
     92453-07 linker command s800.sgs ld PA64 B.11.38 REL 031217

To check the version number: what /bin/ld

To list the installed patches: swlist -l fileset

Grep for "ld" to get the version number for the cumulative ld and linker tools patch.

1.2.3 Agent Controller reports "sh: sysdef: not found" error on Solaris

The Agent Controller uses the sysdef command to obtain the maximum size for a shared memory buffer on your system. If the Agent Controller is unable to run sysdef, it will use dataChannelSize="30M" specified in the <RAServer>/plugins/org.eclipse.hyades.datacollection/pluginconfig.xml file. The following error will be reported on the console where the RAServer.exe was launched:

sh: sysdef: not found

To work around this problem, add the /usr/sbin directory, which contains sysdef, to the PATH variable.

1.2.4 Agent Controller running with a Sun JVM on Linux enters an infinite loop

When running the Agent Controller on a Linux machine with a Sun 1.4.2_04 JVM, the engine enters into an infinite loop. The following messages are logged to the servicelog.log with the last three lines repeated continuously until a kill command is issued to stop the RAServer process:

<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" text="Service starting"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Successfully loaded plugin: org.eclipse.hyades.datacollection"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Successfully loaded plugin: org.eclipse.hyades.logging.parsers"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Successfully loaded plugin: org.eclipse.hyades.test"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Active configuration set to: default"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Loaded configuration: default"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="INFORMATION" 
            text="Service started successfully"/>  
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="Server stopping"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="Internal server closed"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="External server closed"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="Server stopping"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="Internal server closed"/>
<SERVER_MSG time="2004:6:3:17:42:49" severity="WARNING" text="External server closed"/>

To work around this problem, set LD_LIBRARY_PATH pointing to all .so files before starting Agent Controller. For example, before running the RAServer, issue this command:

export LD_LIBRARY_PATH=/opt/j2sdk1.4.2_04/jre/lib/i386/server:/opt/j2sdk1.4.2_04/jre/li
b/i386

1.2.5 Multiple instances of Agent Controller on one machine not permitted

Only one instance of the Agent Controller may be installed on a machine. This means that if you have installed the engine or an extended version of the engine with another product, you will have to uninstall that instance for a new instance to work correctly. For example, some IBM WebSphere Studio or IBM Rational products, or the Autonomic Computing Toolkit from developerWorks, include optional installs of the Agent Controller under the name Agent Controller.

1.2.6 FileNotFoundExceptions not reported by file transfer engine when files on remote server cannot be found

The file transfer protocol does not report a FileNotFoundException when you attempt a GET operation on a nonexistent file from a remote file server. Instead, you are notified of a successful transfer of a file with size 0. If a file of size 0 is returned after a GET operation, it is either because the file does not exist on the remote server or because it exists and is size 0. Currently, the transfer protocol does not differentiate between these two possibilities.

1.2.7 Running the Agent Controller under secured mode on iSeries

Running the Agent Controller under secured mode on iSeries requires special account authorities. The user account used to start the Agent Controller job "RASTART" should have the following special authorities "*SECADM, *ALLOBJ". You may need to add these authorities by updating the user profile using the command "WRKUSRPRF".

1.2.8 Data not collected when monitoring multiple agents simultaneously

Sometimes when monitoring two or more agents associated with a single process simultaneously no data is collected for one of the agents. The data channel for one of the agents fails to initialize properly so no data can be returned to the client from that agent.

To work around this problem, monitor only one agent for a process at a time.

1.2.9 Data bytes are lost when profiling data is transferred through a Zone Labs firewall.

Bugzilla defect: 98031

Data bytes are lost when profiling data is transferred through a Zone Labs firewall. The problem may be more pronounced if the amount of profiling data is large. The work around is to disable the Zone Labs firewall when transferring profiling data.

1.2.10 "Out Of Memory" error when profiling applications

Bugzilla defect: 57786

An "Out Of Memory" error may be issued by the JVM if the JVM arguments -Xmxnnn and -XrunpiAgent are specified when starting the application and the application is attached and monitored with the Profiling and Logging perspective of TPTP. The dataChannelSize attribute setting for the Java Profiling Agent in the Agent Controller configuration may affect the amount of memory available to the JVM which can cause an "Out Of Memory" error. To work around this problem, reduce the -Xmx value or the dataChannelSize value for the Java Profiling Agent or both.

1.2.11 Data collected by agent does not reach the client

Bugzilla defect: 73668

Sometimes when an agent collects data, the data is not sent to the client that is monitoring that agent. The following CommonBaseEvent message in the Agent Controller servicelog.log file shows the cause of the problem:

msg="Shared memory allocation failure: -518"

The shared memory buffer used as the data channel for sending data from the agent to the Agent Controller cannot be allocated. Shared memory buffer names are reused when Agent Controller is restarted. Sometimes the shared memory buffers are not cleaned up completely by the system after a previous use. When attempting to allocate a buffer with a name that was not previously cleaned up, the allocation fails. To work around this problem, perform the monitoring operation again to use a different shared memory buffer name.

1.2.12 Unsuccessful termination of an agent that is running in a process with multiple agents

Bugzilla defect: 100870

When you try to terminate an agent running in a process that has more than one agent, the process is terminated successfully but the status of the process remains unterminated. Repeat attempts to terminate the agent will also be unsuccessful in this case.

To workaround the problem, terminate the agent process at the process level instead of agent level.

1.2.13 Agent Controller crashes if an agent is run in "headless" mode and the logFile attribute is not specified

Bugzilla defect: 102071

The Agent Controller crashes if an agent is run in "headless" mode and the logFile attribute is not specified in the XML file.

The workaround is to ensure that logFile attribute is specified in the XML file when using headless profiling.

1.2.14 An error message is not generated when an invalid path to java.exe is specified in serviceconfig.xml

Bugzilla defect: 100978

The problem occurs on the Linux_x86 platform when an invalid path is specified for java.exe in the serviceconfig.xml file of the agent controller. When a Java application is launched remotely, the workbench should generate the following error message: "Error launching application". The agent controller should also log an error message in its servicelog.log file. Neither one of these results occurs in TPTP version 4. Also note that the 'Terminate' option of the process is enabled, which should not occur.

1.2.15 Remote import of multiple log files through the multiplexed data channel may fail

Bugzilla defect: 101737

When two java processes on AIX, HP-UX and z/OS systems are trying to write data to the control channel a race condition may occur which causes the second java process to hang. The same problem may occur on all supported operating systems when importing multiple log files in a log set scenario. The workaround in both cases is to import log files one at a time waiting for the first log import and corresponding java process to finish before importing another log file.

1.2.16 Multithread capability has to be enabled when running an agent under OS/400 (iSeries)

Bugzilla defect: 104296

Multithread capability has to be enabled when running an agent under OS/400 (iSeries). Under QShell, the environment variable "QIBM_MULTI_THREADED" has to be set to "Y" by this command: "export QIBM_MULTI_THREADED=Y". Otherwise an "AgentControllerUnavailableException" will occur. If the agent is started as a job, the multithread capability has to be enabled by the mean of a job description (JOBD).

1.3 Log and Trace Analyzer

1.3.1 Continuous log monitoring is not supported for localhost

Log and Trace Analyzer does not support continuous log monitoring via localhost. However, if you want to continuously monitor local log files, you can through the loopback interface (127.0.0.1), thus simulating a remote import with a local log file. In this case the logging agent can be at any time terminated to avoid hanging the UI.

To import or continuously monitor via loopback, Agent Controller must be started (not necessary for importing from localhost).

1.3.2 Logging examples readme file does not open

When you create a logging sample project (File > New > Example), a readme file should open in your system browser. However, if the Workbench's file association preferences have not been set correctly, the file may not open.

To fix this problem, go to the File Association preferences page by selecting Window > Preferences and then selecting Workbench > File Associations. In the File types list, select .html. In the Associated editors list, click Add. Select the External Programs button and then select your default browser. Click OK. Click OK to apply the new preference.

1.3.3 Simultaneous clients access using the same database account is not supported

Concurrent client access to a database might lock some tables. To unlock the tables, restart the Workbench and the database server.

1.3.4 Resource path collision

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.

1.3.5 Large Resource Support preferences remain disabled despite valid selection

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.

1.3.6 Improving performance of large log support

To improve the performance of large log support, run the following command after you have imported large logs or created correlations using large logs:

db2 -tvf plugins/org.eclipse.hyades.resources.database_x.x.x
             /scripts/runStatsForAllHyadesTablesDB2-8.1.sql

where x.x.x is the version number on the plug-in directory.

1.3.7 Restart DB2 after creating database and tables

After running the database and tables creation script, CreateDatabaseAndTablesDB2-8.1.sql, you must restart DB2. From a DB2 command window run db2stop and then db2start in order to apply the changes to the configuration parameters made by the script.

1.3.8 Intermittent SQL exception

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.

1.3.9 Importing a log from an IBM iSeries system causes a timeout error message

Bugzilla defect 96020

After starting the Agent Controller on an IBM iSeries system, the first request to import a log file from that system sometimes results in the following message being displayed:

The log import has timed out without importing any data. 
This may be because the Agent Controller configuration file 
contains an invalid configuration. Please contact product support.

However, the import operation succeeds and the log data is displayed in the Log view.

1.3.10 Remote Log Import from HP-UX system with a filter causes a NullPointerException error message

Bugzilla defect 96040

A request to import a log file from an HP-UX system with a filter specified sometimes results in the following message being displayed:

An internal error occurred during: "Importing log file...".
java.lang.NullPointerException 
org.eclipse.hyades.internal.execution.core.file.FileServerCommandFactory.getInstance(FileServerCommandFactory.java)
org.eclipse.hyades.execution.local.file.FileManagerExtendedImpl.<init>(FileManagerExtendedImpl.java)
org.eclipse.hyades.execution.local.file.FileManagerFactory.create(FileManagerFactory.java)
org.eclipse.hyades.log.ui.internal.util.GLAFilterHelper.deleteTempAdapter(GLAFilterHelper.java)
org.eclipse.hyades.log.ui.internal.wizards.ImportLogWizard$RemoteLogImportJob.run(ImportLogWizard.java)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

However, the import operation succeeds and the log data is displayed in the Log View.

1.3.11 Remote Log Import with a filter does not work when Agent Controller is started incorrectly

Bugzilla defect 95615

A request to import a log file from a non-Windows system with a filter specified results in the following message being displayed when the Agent Controller is started incorrectly:

"An error occurred while attempting to import the log file /home/user/app.log.
Reason: [Ljava.lang.StackTraceElement;@538c718"

The following exception is thrown as a result of this error and is logged to the .log file. Finding this exception in the .log file is also indicative of the Agent Controller being started incorrectly:

org.eclipse.hyades.internal.execution.core.file.ServerNotAvailableException: 
java.net.ConnectException: Connection refused: connect

Ensure that the directories of the JRE that contain executable libraries such as libjvm.so are added to the appropriate library path environment variable for the system before starting Agent Controller.  Refer to the getting_started.html file located in the Agent Controller installation directory for more details.

1.3.12 Unreadable data in some events when importing Microsoft Windows System event log on DBCS system

Bugzilla defect 95077

Importing the Microsoft Windows System event log from a Double Byte Character Set system may result in some Common Base Events being shown in the Log View with missing or unreadable msg values.

1.3.13 Importing Windows Application event log generates Common Base Event formatting errors

Bugzilla defect 101718

Sometimes when importing the Microsoft Windows Application event log the following messages are displayed:

IWAT0027E Error importing the specified log file(s).
IWAT0412E Errors occurred parsing the log file null.
IWAT0438E Common Base Event formatter N6B1EE3005B511D880008CD5D1F4FA98 cannot
create a CommmonBaseEvent because required property creationTime is missing.

The log parser fails to parse some log records properly. However, most log records are imported and shown in the Log view.

1.3.14 Importing Windows event log with a filter fails

Bugzilla defect 108958

Importing a Microsoft Windows event log with a filter specified fails with the following error messages. To work around this problem, import the Windows event log without a filter and then use the Log View filter dialog to filter the events in the Log View.

IWAT0027E Error importing the specified log file(s).
  IWAT0412E Errors occurred parsing the log file null.
  java.lang.Exception: IWAT0239E Converter command failed: java.io.IOException: 
CreateProcess: eventlogreader.exe application error.log error=2

1.3.15 Importing a log file from a remote z/OS system may result in incomplete data

Bugzilla defect: 80730

Importing a log file using Log and Trace Analyzer from a remote z/OS system may result in incomplete data shown in the Log View. The import operation may stop prematurely and not all of the log records are shown in the Log View. This problem occurs when one of the following IBM JDK versions is installed on the z/OS system:

This problem is fixed in IBM JDK 1.4.2 with PTF UK00802.  Upgrade the JDK to that version or a later version.  If you cannot upgrade the JDK version, to work around the problem, change the configuration of the Agent Controller on the z/OS system by doing the following steps:

  1. Edit the file plugins/org.eclipse.hyades.logging.parsers/config/pluginconfig.xml in the Agent Controller install directory.
  2. Add a new Parameter to the RemoteLogParserLoader Application element after the java.version parameter. For example:
    <Parameter position="prepend" value="-Djava.version=1.4"/>
    <Parameter position="prepend" value="-Djava.compiler=NONE"/>
    <Parameter position="append" value="&quot;config_path=%GLA_CONFIG_PATH%&quot;"/>
  3. Restart Agent Controller.
  4. Import the log file again.

1.4 Probekit

1.4.1 Probekit may fail to instrument certain large Java methods

Bugzilla defect: 63336

The Probekit may fail to instrument certain large Java methods. If Probekit's byte- code insertion causes a method to grow so large that interior branches can no longer reach their targets, the Probekit will throw an exception and instrumentation will fail.

1.5 Profiling Tool

1.5.1 Problem with garbage collection when using IBM JDK 1.4.1

Bugzilla defect: 56182

If the user's application uses an extremely large amount of heap space, requesting Collect Object References or Run GC, can potentially cause the JVM to crash with the following error message:

 **Out of memory, aborting**

 *** panic: JVMCI023: Cannot allocate memory to collect heap dump in jvmpi_heap_dump

 abnormal program termination

You can try to work around this by running without the -Xmx parameter, if you are currently running with it.

1.5.2 With Sun JDK, some method calls are not traced

Bugzilla defect: 69051

Using the Sun JDK on Windows, certain method calls in Java programs are not being traced by JVMPI.

There is no known workaround.

1.5.3 Profiling on Solaris using the Sun JDK 1.4.x or on HP using the HP JDK 1.4.x may cause JVM to crash

Bugzilla defect:56404

Profiling on Solaris using the Sun JDK 1.4.x or on HP using the HP JDK 1.4.x may cause the JVM to crash.

The problem is due to a bug in the JVM. To work around this problem, use only one of the following profiling sets:

The problem arises if you use these profiling sets in combination or if "Show instance level" information is turned on.

Alternatively, you can upgrade to the JDK 1.4.2_08-b03 build on Sun or the JDK 1.4.2_04 build on HP, both of which fix the problem.

1.5.4 Potential crash when running in standalone mode with STACK_INFORMATION=contiguous on Solaris

Bugzilla defect: 50090
When profiling on Solaris, you may encounter problems with standalone profiling. The problem only occurs when STACK_INFORMATION=contiguous (or boundaryAndContiguous) and TRACE_MODE=full. This problem may result in your JVM crashing.

To work around this problem with STACK_INFORMATION=contiguous, set TRACE_MODE=noObjectCorrelation. The problem does not occur when STACK_INFORMATION=none or STACK_INFORMATION=normal.

1.5.5 Negative timeout values for WAIT and WAITED events

Bugzilla defect: 63969

When running with IBM 1.4.2 JDK, with the jvmpi profile option 'MONITOR_MODE=all' (in standalone mode), you may see negative timeout attributes on monitorWait and monitorWaited elements in their trace. These are actually extremely large timeout values cast as positive 64 bit integers. This bug is the result of a JDK bug.

The JDK bug has been fixed as of IBM JDK 1.4.2 SR1a. A solution is to upgrade to this JDK level or later.

1.5.6 Incorrect monitor dumps with IBM JDK 1.4.2

Bugzilla defects: 65193 and 72180

Because of a JDK bug, when running the Test and Performance Platform in standalone mode with the jvmpi profile option 'MONITOR_MODE=all', you may get incorrect monitor dumps. For bug 65193 particularly, this happens when the '-Xj9' VM argument is used.

1.5.7 Method counts incorrect with JIT inlining

Bugzilla defect70660 (closed as "Won't fix")

If you suspect that the method counts you are seeing in the analysis tools are too low, turn off JIT inlining, if you are using it. This problem happens only when with the IBM Java 2 Runtime Environment v.1.4.2, and only when JIT is enabled.

The only work-around for this problem is to turn off inlining. To do this, set the following environment variable:

JITC_COMPILEOPT=NINLINING

1.5.8 Method level CPU time statistics limitations on AIX and Solaris

In Test and Performance Tools Platform versions 3 and 4, method level CPU time statistics are available for collection. Optionally, you can view method level CPU time statistics in an additional column in the Method Statistics view or Method Invocation table. Platform limitations for this feature are as follows:

There is no support for method level CPU time statistics reporting on AIX 4.3.

On AIX Version 5.1, method level CPU time statistics reporting requires that the environment variable "AIXTHREAD_ENRUSG=ON" be exported.

The method level CPU time statistics feature is currently not supported on Solaris.

1.5.9 Profiling to an existing profile file fails on Linux

Bugzilla defect: 95803

Profiling to an existing profile file fails on Linux platforms. An invalid path separator is used in the code which results in a FileNotFoundException.

To workaround the problem, profile to a new file instead of an existing profile file.

1.5.10 Importing profile files generated from headless profiling

When a profile file is generated from headless profiling, the file cannot be imported to the Eclipse workbench properly because it is missing the top level <TRACE> element.

The workaround is to manually edit the profile file add the strings <TRACE> at the beginning and </TRACE> at the end of the profile file before importing into the Eclipse workbench.

1.5.11 Import profile file with package level filtering shows empty view

Bugzilla defect: 100334

When the profile file is generated with Memory Analysis (profiling type) selected, events will not be saved in the profile file in chronological sequence. This causes failures such as lost packages when the profile file is subsequently imported using filtering at the package level.

To workaround the problem, import the profile file without any filtering at the package level and filter the data in statistic views after the import is complete.

1.5.12 Profiling mode shows more data than expected

When profiling an application with the following profiling types: Basic Memory Analysis with no instance level information and Execution Time Analysis with execution flow graphical details no instance level information, the instance level information will show up in Execution Statistics view when the Instance Level Information toolbar button is selected.

1.5.13 Free Up Memory action saves only selected resources in the Profiling Monitor view

Bugzilla defect: 101932

When invoking the Free up Memory action, a dialog prompts the user to select the resources to be saved before the memory is deallocated. However, the action only saves the resources selected in the Profiling Monitor view and ignores the selection made in the dialog.

To workaround the problem, explicitly save all resources in Profiling Monitor view before invoking the Free Up Memory action.

1.5.14 "Execution History - Full Graphical Details" profiling set involves collection of boundary classes

Bugzilla defect: 106793

The "Execution History - Full Graphical Details" profiling set (accessible via Run > Profile... > New > Profiling Tab > Overview Tab) differs significantly from the v3.2 "Execution History" profiling set.

In version 3.3 the original "Execution History" profiling set was renamed to "Execution History - Statistical" in order to facilitate addition of the new graphical profiling set called "Execution History - Full Graphical Details". The "Execution History - Statistical" set should be used in place of "Execution History" in version 3.3 onwards.

The "Execution History - Full Graphical Details" set differs significantly from the original "Execution History". Among other things, the "Collect boundary classes excluded by the filter set" option is selected by default in the graphical execution set, which involves the collection of extra classes and methods.

1.6 Statistical Console

N/A

1.7 Test

1.7.1 Common Test Issues

1.7.1.1 National characters are currently not supported in creating test suites and test cases

Bugzilla defect: 88029

National characters are currently not supported in creating test suites and test cases. The Agent Controller will not be able to handle those characters and the execution of the test will fail.

The workaround for this problem is to use standard ASCII characters when creating test suites and test cases.

1.7.2 URL Test

N/A

1.8 Charting Service

1.8.1 SVG filter effects are not supported in Mozilla native SVG browsers

The current Mozilla native SVG enabled browsers do not fully support the SVG 1.0 specification. Specifically, filter effects that provide shading for 3-D horizontal, vertical, and stack bar charts are not supported. In additional the scatter chart highlighting effect is not functional in Mozilla native SVG enabled browsers.

1.8.2 The Adobe SVG v3.0 plug-in is required to view test reports in Internet Explorer.

The Adobe SVG v3.0 plug-in or a later version is required to view test reports in Internet Explorer. The Adobe SVG Viewer can be downloaded at the Adobe SVG Web site.

1.8.3 Hungarian is not supported by SVG Adobe Viewer 3.0

Bugzilla defect: 88786

The SVG charts generated by the charting service were tested with Adobe SVG Viewer 3.0. Adobe does not provide an SVG Viewer 3.0 that supports Hungarian. Go to http://www.adobe.com/svg/ to view supported languages.