IBM Support

WebSphere Application Server Performance Tuning Toolkit

How To


The WebSphere Application Server Performance Tuning Toolkit (PTT) is an Eclipse-based GUI tool to access live Traditional WebSphere Application Server (tWAS) Performance Monitoring Infrastructure (PMI) data. The tool is provided as is without any warranty or support.


  1. Download:
    1. Windows:
    2. Linux:
    3. macOS:
      1. Before extracting, open Terminal and run: xattr -d*
  2. Ensure Java 8 (64-bit) is on your PATH or create a "jre" directory under the PTT folder and copy a Java installation into it. Java 11 or higher will not work.
  3. Start PTT by double clicking on ptt.exe/ptt/, or from the terminal to show console output:
    1. Windows: ptt.exe
    2. Linux: ./ptt
    3. macOS: ./
  4. Click add a new host and provide the details of the deployment manager or application server, including its SOAP port.
  5. Select the host and click connect to selected host.
  6. Click yes to monitor all servers.
  7. In the topology view, click the target server and click open monitor page.
  8. The PMI data will update live, approximately every 60 seconds or so.

Additional Information

Important Notes
  1. PTT is provided as is without any warranty or support.
  2. There is a self-placed lab that has PTT installed: WebSphere Application Server Troubleshooting and Performance Lab on Docker.
  3. Note that tuning assistance is not in the scope of IBM support. If you need tuning assistance, please contact your IBM account representative to set up a paid services engagement with a skilled performance tuning resource.
Revision History
  • V1.0.20200908
    • Fix report generation.
    • Fix preference retrieval.
  • V1.0.20200728
    • Add error details to connection exceptions.
    • Add support for an optional -Dinsecure=true option that avoids "peer not authenticated" and hostname verification errors when the normal solutions are difficult or infeasible.
  • V1.0.20200701_2
    • Fix error on Windows: SSLSocketFactory is null. This can occur if is called to create a socket and* properties are not set.
    • Set by default
  • V1.0.20200630_4
    • Allow using OpenJDK in addition to IBM Java
  • V1.0.20200629
    • Make debugging easier
  • V1.0.20200624
    • Create 64-bit builds for Windows, Linux, and macOS on top of a more modern Eclipse 2020-06.
If you have a problem, perform the following steps to gather diagnostics:
  1. On Windows, copy ptt.ini to eclipse.ini and edit eclipse.ini. On Linux, edit ptt.ini. On macOS, edit
    1. Change the following line:


      To this:

    2. Change the following line:

      To this:
  2. Edit TraceSettings.txt (on macOS,
    1. Change the following line:


      To this:

  3. Open a command prompt or terminal and start PTT as follows:

    C:\Users\name\> cd Downloads\PTT
    C:\Users\name\Downloads\PTT> .\eclipsec.exe -debug -consoleLog > ptttrace.log 2>&1

    % cd Downloads/PTT/
    % ./ptt -debug -consoleLog > ptttrace.log 2>&1

    $ cd Downloads/PTT
    $ ./ptt -debug -consoleLog > ptttrace.log 2>&1
  4. Reproduce the problem and close PTT
  5. Send ptttrace.log and adminclient.log (on macOS, the files are in ./
Known Issues
  1. Symptom:
    [SOAPException: faultCode=SOAP-ENV:Client; msg=Error making SOAP call: java.lang.ClassNotFoundException:; targetException=java.lang.IllegalArgumentException: Error making SOAP call: java.lang.ClassNotFoundException:]

    Solution 1: Launch PTT with IBM Java 8 64-bit (see #4 below)


    Solution 2:
    2a. Edit ptt.ini (on macOS,
    2b. Add to the bottom and replace PTTDIRECTORY with the absolute path to the PTT installation directory (on macOS, .../
  2. Symptom:
    [SOAPException: faultCode=SOAP-ENV:Client; msg=Error making SOAP call: hostname in certificate didn&apos;t match: &lt;; != &lt;localhost&gt;; targetException=java.lang.IllegalArgumentException: Error making SOAP call: hostname in certificate didn't match: <localhost> != <myserver>]

    Solution 1: Edit the host in PTT and change the Hostname to what is specified in the second set of <>'s in the error message above (in this example, myserver).


    Solution 2: If you're willing to run without hostname verification, edit ptt.ini (on macOS, and add:
  3. Symptom:
    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error making SOAP call: peer not authenticated; targetException=java.lang.IllegalArgumentException: Error making SOAP call: peer not authenticated]

    Solution 1: Download the certificate from WAS and add it to PTT's trust store (DummyClientTrustFile.jks). The DummyClientTrustFile.jks is in a subdirectory of PTT such as configuration/org.eclipse.osgi/bundles/5/1/.cp/etc/. Example importing on POSIX-based systems (replace localhost:8880 with your WAS host and SOAP port):

    echo -n | openssl s_client -connect localhost:8880 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > was.cert
    keytool -importcert -alias "was" -file was.cert -keystore DummyClientTrustFile.jks -storepass WebAS


    Solution 2: If you're willing to run without certificate verification, edit ptt.ini (on macOS, and add:
  4. For various connection issues, it may help for PTT to run with IBM Java instead of Oracle/OpenJDK/HotSpot/OpenJ9:
    1. On Windows, download IBM Java 8 64-bit from here: and then extract it and copy the JDK folder into the PTT folder and then rename it to jre and restart
  5. To connect using TLS 1.2, follow the instructions for configuring administrative clients: PTT dynamically generates files in a directory under the installation folder after the first connection is attempted. For example: configuration/org.eclipse.osgi/bundles/5/1/.cp/etc/. The TLSv1.2 changes are only needed in the ssl.client.props file.
  6. Symptom:
    java.lang.NoClassDefFoundError: org.omg.CORBA.UserException
        at java.base/java.lang.ClassLoader.defineClassImpl(Native Method)
        at java.base/java.lang.ClassLoader.defineClassInternal(
        at java.base/java.lang.ClassLoader.defineClass(
        at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(
        at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(
        at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(
        at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(
        at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(
        at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(
        at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(
        at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
        at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(
        at java.base/java.lang.ClassLoader.loadClass(
    Caused by: java.lang.ClassNotFoundException: org.omg.CORBA.UserException cannot be found by
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
        at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(
        at java.base/java.lang.ClassLoader.loadClass(

    Solution: This is caused by Java >= 11. Instead, use Java 8. Hopefully one day we can get newer versions of Java to work.

For details, contact Kevin Grigorenko (

Document Location


[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000L2DEAA0","label":"PMI"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
20 January 2021