42 lines
3.0 KiB
HTML
42 lines
3.0 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Java execution modes</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><A NAME="clsjvamode">Java execution modes</A></h5>
|
||
|
|
|
||
|
|
|
||
|
|
<p>Because all WebSphere components (servlets and JSPs) are loaded by an application server classloader, application classloader, and application module classloader, WebSphere components do not use the direct execution (DE) capabilities of the i5/OS Java Virtual Machine. Java program (JVAPGM) objects are not used when running WebSphere component code. Classes loaded by a Java Virtual Machine classloader or the WebSphere extension classloader use DE capabilities and JVAPGM objects. Java user classloader caching can be used to allow WebSphere components to use permanent JVAPGM objects and DE capabilities, though this is not necessary for the vast majority of applications. </p>
|
||
|
|
|
||
|
|
<p>By default, application servers run with the Java system property java.compiler=jitc_de. The jitc_de value means that just-in-time compilation is done for any Java object for which a JVAPGM object does not exist (or cannot be used, in the case of WebSphere application classloaders). This setting provides the best overall performance.</p>
|
||
|
|
|
||
|
|
<p>It is possible to change application servers to use direct execution instead of JIT mode. Doing so results in longer startup times, because creation of the JVAPGM takes longer than creation of the JIT stubs. Due to performance improvements in the JIT run time, performance of direct execution even after JVAPGM creation is probably slower also. To make an application server use direct execution for all classes, perform these steps:</p>
|
||
|
|
<ol>
|
||
|
|
|
||
|
|
<li>In the WebSphere administrative console click <strong>Servers --> Application Servers --> <em>server_name</em></strong>.</li>
|
||
|
|
<li>In the <strong>Additional properties</strong> section, click <strong>Process Definition</strong>.</li>
|
||
|
|
<li>In the <strong>Additional properties</strong> section, click <strong>Java Virtual machine</strong>.</li>
|
||
|
|
<li>In the <strong>Additional properties</strong> section, click <strong>Custom Properties</strong>.</li>
|
||
|
|
<li>Click <strong>New</strong> to add a property. Add these properties:
|
||
|
|
<ul>
|
||
|
|
<li>Property java.compiler with value NONE </li>
|
||
|
|
<li>Property os400.defineClass.optLevel with a value that indicates the optimization level desired (values are 0 for interpret, and 10, 20, 30, or 40 for direct execution optimization levels)</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
|
||
|
|
<p>It is also possible to have an application server use the interpreter only (no JIT). To make an application server use full interpretation for all WebSphere components, add Java system property java.compiler with value NONE.</p>
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|