Profiling and logging tools - release notes

1.0 Introduction
2.0 Changes from the previous release
3.0 Known problems and limitations
   3.1 Profiling restrictions for JDK levels on OS/390, z/OS
   3.2 Disable JIT when profiling applications on all flavors of Linux 390 for JVM's older than J2RE 1.3.1 IBM build cx390131-20020404
   3.3 Profiling filters are incompatible between WebSphere Studio Versions 4.x and Version 5.0
   3.4 Data is not captured during multiple monitoring sessions
   3.5 No console output for an attached application
   3.6 Logging a Thread object results in logging the current thread
   3.7 Log files cannot be opened with Microsoft WordPad while WebSphere Studio is running
   3.8 Character encoding issues
   3.9 HP-UX: No support for profiling the JVM in HotSpot mode for JDK levels below 1.3.1.01
   3.10 Disable JIT when profiling WebSphere Version 4 Test Environment using the Server perspective
   3.11 Disable JIT when profiling the WebSphere Application Server Version 4.x on AIX
   3.12 Classes residing on network drives are not accessible
   3.13 Importing a WebSphere Application Server log file either from or to a non-English host is not supported
   3.14 Disable JIT when profiling on Solaris
   3.15 The Agent Controller is not installed automatically with the product
   3.16 The log_file_name_Viewer.xml XML viewer cannot be viewed in Internet Explorer Version 5.x or below
   3.17 The log_file_name_Viewer.xml XML viewer's XSL stylesheet adds a new line character for each '(' character when displayed in Internet Explorer Version 6.x or above
   3.18 Cannot launch a Java process if the last segment of the class path contains non-ASCII characters
   3.19 Cannot launch a Java class when the class name contains non-ASCII characters
   3.20 The Instance Statistic view and the Heap view have been removed from the profiling tools

1.0 Introduction

This readme covers the performance and memory profiling and analysis tools that are available from the Profiling perspective of the workbench (including the Log views).

The online help for the profiling tools contains more information on WebSphere test environment and Java restrictions, and on working around them.

2.0 Changes from the previous release

Heap view and Method Execution view are no longer available. Object Reference view has been replaced by an Object Reference table. This may cause an error message indicating a problem restoring the Workbench. Such an error message may be ignored.

3.0 Known problems and limitations

3.1 Profiling restrictions for JDK levels on OS/390, z/OS

Using some levels of the IBM Developer Kit for OS/390, Java 2 Technology Edition may cause incorrect profiling data to be collected and displayed. The levels affected are PTF's UQ99325, UQ59962, and UQ61198.

Workaround: If you have one of the PTF's UQ99325, UQ59962, or UQ61198 for IBM Developer Kit for OS/390, Java 2 Technology Edition installed, please profile your OS/390 or z/OS Java applications with the JIT compiler disabled by specifying the VM parameter -Djava.compiler=NONE

3.2 Disable JIT when profiling applications on all flavors of Linux 390 for JVM's older than J2RE 1.3.1 IBM build cx390131-20020404

If the JVM is older than J2RE 1.3.1 IBM build cx390131-20020404, you will need to disable the JIT in order to profile on Linux 390.

You can determine the date of your JVM by running the command java -fullversion. In order to disable the JIT, define a system property java.compiler with a value of NONE. This can be done on the command line of your process by adding the parameter -Djava.compiler=NONE.

3.3 Profiling filters are incompatible between WebSphere Studio Versions 4.x and Version 5.0

Profiling filters will not be honored when using the Version 5 workbench with a Version 4 profiling agent. They will, however, be honored by the profiling agent when used by a Version 4 workbench.

3.4 Data is not captured during multiple monitoring sessions

If no profiled methods are invoked subsequent to restarting a monitoring session, then data for pre-existing elements may not be updated correctly.

3.5 No console output for an attached application

When you attach to an existing process, the console output will not be captured by the Profiling Console view.

3.6 Logging a Thread object results in logging the current thread

Logging a Thread object results in logging the current executing thread. The resultant backtrace is created using the current thread and does not reflect the logged thread.

3.7 Log files cannot be opened with Microsoft WordPad while WebSphere Studio is running

Log files cannot be opened with Microsoft WordPad while WebSphere Studio is running.

Workaround: Real-time viewing of WebSphere Studio log files can be done either with all other text editors, or the log_file_name_Viewer.xml XML viewer and an XML-enabled Web browser.

3.8 Character encoding issues

If the character encoding for your remote application platform is different from the character encoding for the platform you are running WebSphere Studio on, the console message in the Profiling Console view will not be displayed correctly.

3.9 HP-UX: No support for profiling the JVM in HotSpot mode for JDK levels below 1.3.1.01

For JDK levels below 1.3.1.01, profiling of applications launched by WebSphere Studio is done, by default, in Classic mode. For JDK levels 1.3.1.01 and above, if you want to profile your application using WebSphere Studio in HotSpot mode, follow these steps:

  1. Look for the file serviceconfig.xml on your HP-UX machine in the /opt/IBMRAC/config directory.
  2. Edit this file by removing the following line of text:
    Parameter value="-classic" position="prepend"/

For JDK levels below 1.3.1.01, if you want to profile your application using the command line, add the -classic option. For example, to profile an application (PerformanceExample.java) in stand-alone mode, using filters that are defined in the file myFilters.txt, and directing the data from the profiling session to a file called PEProfilingData, type the following on a command line (all on one line):
java -classic -
XrunpiAgent:server=standalone,filters=myFilters.txt,file=PEProfilingData.trcxml
PerformanceExample

3.10 Disable JIT when profiling WebSphere Version 4 Test Environment using the Server perspective

The JIT must be disabled when profiling the WebSphere Version 4 test environment using the Server perspective. In order to do this, you must define a system property java.compiler with a value of NONE within the server configuration before launching the server in profiling mode.

3.11 Disable JIT when profiling the WebSphere Application Server Version 4.x on AIX

The JIT must be disabled when profiling the WebSphere Application Server Version 4.x on AIX. This can be done by defining the system property java.compiler with a value of NONE before launching the application server.

3.12 Classes residing on network drives are not accessible

The IBM Agent Controller service is configured to log on as "Local System Account". Therefore, it might not have the rights to access mounted network drives, which are usually being net use'd by the current user ID. If you want to let the RAC use the classes on network drives, do the following:

  1. Open the Windows "Services" window
  2. Select "IBM Agent Controller"
  3. Click the "Properties" toolbar button
  4. Select the "Log On" pane
  5. Select the "This account" radio button and fill in the user ID information (the user ID which net use'd the drive)
  6. Click OK
  7. Restart the "IBM Agent Controller" service
  8. Relaunch the application

NOTE: This will allow the use of network drives, but will limit the RAC's access rights to whatever the current user has.

3.13 Importing a WebSphere Application Server log file either from or to a non-English host is not supported

A WebSphere Application Server log file that is imported into WebSphere Studio from a non-English host (File > Import > WebSphere Application Server Log File) will not be parsed correctly. A message may appear with a warning about the problem. WebSphere Studio also does not support importing a WebSphere Application Server log file if it is installed on a non-English host.

Workaround: Change the platform locale to English on the host where the WebSphere Application Server log file resides.

3.14 Disable JIT when profiling on Solaris

The JIT must be disabled when profiling on Solaris. In order to do this provide -Djava.compiler=NONE to the command line when launching applications to be profiled. When profiling the application server on Solaris, define the system property java.compiler with a value of NONE before launching the application server.

3.15 The Agent Controller is not installed automatically with the product

The Agent Controller is no longer installed automatically when you install WebSphere Studio. For more Agent Controller installation information, refer to the Installation Guide.

3.16 The log_file_name_Viewer.xml XML viewer cannot be viewed in Internet Explorer Version 5.x or below

The log_file_name_Viewer.xml XML viewer cannot be viewed in Internet Explorer Version 5.x or below due to a limitation in its XSL engine.

Workaround: View the log_file_name_Viewer.xml XML viewer in Internet Explorer Version 6.x and above or another XML- or XSL-enabled Web browser.

3.17 The log_file_name_Viewer.xml XML viewer's XSL stylesheet adds a new line character for each '(' character when displayed in Internet Explorer Version 6.x or above

The log_file_name_Viewer.xml XML viewer's XSL stylesheet adds a new line character for each '(' character when displayed in Internet Explorer Version 6.x or above due to a limitation in its XSL engine.

3.18 Cannot launch a Java process if the last segment of the class path contains non-ASCII characters

Workaround: Append an ASCII path fragment at the end of the class path entry.

3.19 Cannot launch a Java class when the class name contains non-ASCII characters

Use only ASCII characters for the class name.

3.20 The Instance Statistic view and the Heap view have been removed from the profiling tools

When you migrate a workspace from Version 5.0 (General Availability) to Version 5.0.1, you receive a "Problems occurred restoring workbench" pop-up error message just after migrating the workspace if the Profiling perspective is open at the time and the Heap or Instance Statistic views were visible in the Profiling perspective. This is due to the removal of the Heap view and the Instance Statistic view in Version 5.0.1. This error appears if the Profiling perspective is open in the workspace at the time of migration, and it can safely be ignored by clicking OK.

Return to the main readme file