Enabling hot method replace for a WebSphere Application Server v6.0.x

If you want to make changes to your Java™ classes while you are debugging, you can set this preference by editing the server before you start it. When hot method replace is enabled most application changes is picked up automatically without requiring an application or server restart.
Restriction:
  • For WebSphere® Application Server v6.1.x local or remote server, the hot method replace is always enabled in debug mode.
To enable hot method replace for a WebSphere Application Server v6.0.x1 local or remote server:
  1. In the Servers view, double-click your WebSphere Application Server v6.0.x to open the server editor.
  2. Click the Overview tab.
  3. Expand the Server section, and select the Enable hot method replace in debug mode check box.
  4. Save and close the editor.
  5. Start the server in debug mode. When the server is started in debug mode, class file changes will be picked up by the server automatically.
Note:
  • To debug a stand-alone application using hot method replace, you must use this product's provided JRE found in x:\eclipse\jre, where x is the directory where this product is installed and you must specify -Xj9 as a VM argument.
  • Hot-method replace cannot be used while profiling an application. When you profile an application, data related to the program's runtime behavior is collected and presented in both graphical and tabular views. Profiling enables you to see which operations take the most time and helps you to find and solve memory leaks. For more information, refer to the Profiling and logging documentation.
  • When using hot method replace to debug servlets, the server will reload a method which is changed. It will not reload the class or reload and reinitialize the servlet.
  • JSP debugging does not support hot method replace.
  • When hot method replace is enabled, the JIT compiler is also enabled. The JIT compiler used when Hot-method replace is enabled, is much faster than when using normal debugging. The JAVA_COMPILER=NONE environment variable and system property -Djava.compiler=NONE to disable the JIT compiler will be ignored if hot method replace is enabled when debugging an application. When hot method replace is enabled, the -Xint option will disable the JIT compiler.
Related information
WebSphere Application Server maintenance releases
1 Not available in WebSphere Application Server Toolkit V6.1.x, but available in products such as Rational® Application Developer V7.0.x or Rational Software Architect V7.0.x

Feedback