Stand-Alone J Optimizer 2009 Readme

By: Mark Deckert

Abstract: Stand-Alone J Optimizer 2009 Readme

    Embarcadero® J Optimizer™ 2009 Readme

For updates to these notes, see http://dn.embarcadero.com/article/39334.

J Optimizer equips Java developers with a comprehensive toolkit for optimizing application performance and quality. Stand-alone J Optimizer provides full profiling capability without requiring integration into an IDE or a larger development environment. You can use J Optimizer to profile memory and CPU usage, display real-time threading information, and determine which parts of your code are actually being executed. You can also track performance bottlenecks at the JDBC, JMS, JNDI, JSP, EJB, CCI, and Web Services levels, and locate the exact line of source code for root-cause analysis. You can also run source code Audits and Metrics in J Optimizer.

Touchpoint is a set of integration plug-ins that enables developers to use the J Optimizer configuration tools from within their own Eclipse-based development environment or IDE. See touchpoint_readme.html for the Touchpoint readme.

The Agent runs inside the Java virtual machine that is running the testing session and collects data. See agent_readme.html for the Agent readme.

    Known Issues

The following are known issues in this build:
ID Number Summary
8243
TPTP: Error occurs when launching profile configuration: "IWAT0453E An error occurred when connecting to the host".
Workaround:
Windows TPTP requisites can be found here
Linux TPTP requisities can be found here
7029 Out of memory error when profiling Eclipse plug-in applications and saving snapshots with Reference Graph and Memory Leak data included
Workaround: Launch Eclipse plug-in application with VM arguments: -Xms128m -Xmx896m -XX:MaxPermSize=256m
Do not save snapshots with reference graph and memory leak data included.
8071 Attach - J Opti agent launch configuration is not listed in the Profile Configurations dialog
Workaround: Launch run configurations (Run|Run Configurations...) before launching the Profile Configurations dialog.
8234 Java Profiling stops just after switching to memory leak view on Red Hat Enterprise Linux 5.0.
Workaround: Change the SELinux policy setting.
Click on System -> Administration -> Security Level and Firewall -> SELinux Tab. Change "Enforce" to "Permisive"
OR
Click on System -> Administration -> Security Level and Firewall-> SELinux tab ->Modify SELinux Policy ->Compatibility -> Allow the use of shared libraries with Text Relocation
7780 Macintosh: Profiling SWT applications starts the application in the background
The VM argument "-XstartOnFirstThread" option should be added to the profile launch configuration in the Arguments tab.
8292
J Optimizer uses the default workspace JRE instead of the project's JRE.
Workaround: Make the project JRE the default JRE in Window|Preferences, Java|Installed JREs.
8508
Vista: Operations that require the creation of temporary files fail when the TEMP and TMP system variables are set to USER_HOME/Local Settings.. with User Access Control (UAC) enabled for the user account. For example, this failure can occur when trying to generate a snapshot.
Workaround: Either one of the 3 workarounds listed below can be applied in this case:
  1. Provide administrative rights to the user account
  2. Right click on JOptimizer.exe in the J Optimizer home directory and select 'Run as Administrator'
  3. Modify the TEMP and TMP system variables to any directory in the file system for which the user has write permissions. Restart JOptimizer after doing this.
  4. Disable User Access Control (UAC) for the account. To do this, run regedit as Adminstrator and run regedit in Admin mode and change the value of the following key to zero
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA


Server Response from: ETNASC01