Example: Setting Custom JVM Properties

In the WebSphere Application Server administrative console, you can change the values of the following custom JVM properties:

com.ibm.websphere.bean.delete.sleep.time
Specifies the time between sweeps to check for timed out beans. The value is entered in seconds. For example, a value of 120 would be 2 minutes. This property also controls the interval in the Servant process that checks for timed out beans still visible to the EJB container.

The default value is 4200 (70 minutes). The minimum value is 60 (1 minute). The value can be changed through the administrative console. To apply this property, you must specify the value in both the Control and Servant JVM Custom Properties.

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties panel. For example, click Servers > Application Servers > Controlserver1 > Process Definition > Control > Java Virtual Machine > Custom Properties to define the property in the control, or Application Server >server1 > Process Definition > Servant > Java Virtual Machine > Custom Properties to define the property in the servant.
  2. If the com.ibm.websphere.bean.delete.sleep.time property is not present in the list, click New.
  3. Enter com.ibm.websphere.bean.delete.sleep.time in the name field, and specify an appropriate time, in seconds, in the Value field.
com.ibm.websphere.network.useMultiHome

In a multihomed environment where WebSphere Application Server is restricted to listen only on a specific IP address for Discovery and SOAP messages, set this property to false for the deployment manager, all Application Servers, all node agents, and the Deamon (z/OS Location Service) .

By default, the value of the property is true and the application server listens on all IP addresses on the host for Discovery and SOAP messages.

If the property is set to false, WebSphere Application Server will only listen for Discovery and SOAP messages on the configured host name. If you set the property to false, you must also:

You can change the value through the administrative console. Modify the defaults by setting the value for the server, deployment manager, and node agent. In order for these changes to take place, you must restart the server.

Steps for this task

  1. To set this property, connect to the administrative console and navigate to the indicated page.
    Application server Servers > Application Servers >server1 > Process Definition > Control > Java Virtual Machine > Custom Properties
    Deployment manager System Administration > Deployment Manager > Process definition > Control > Java Virtual Machine > Custom Properties
    Node agent System Administration >Node Agent > nodeagent > Process definition >Control > Java Virtual Machine > Custom Properties
  2. If the com.ibm.websphere.network.useMultiHome property is not present in the list, click New to create a new property
  3. Specify com.ibm.websphere.network.useMultiHome in the Name field, and false in the Value field.
  4. To ensure the correct host is specified for the End Point property, navigate to the indicated page.
    Application server Servers > Application Servers >server1 > End Points > end_point_name
    Deployment manager System Administration > Deployment Manager > > End Points > end_point_name
    Node agent System Administration >Node Agent > nodeagent > End Points > end_point_name

    Note: For the node agents, there is a MULTICAST port NODE_MULTICAST_DISCOVERY_ADDRESS.

  5. Restart the server.
com.ibm.ejs.am.mode.workbased
Specifies the behavior of the Alarm Manager. By default, the Alarm Manager is set to on. Use this property to set the Alarm Manager to quiet mode (off).

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties panel. For example, Servers > Application Servers >server1 > Process Definition > Servant > Java Virtual Machine > Custom Properties
  2. If the com.ibm.ejs.am.mode.workbased property is not present in the list, click New to create a new property name. The New custom properties panel appears.
  3. Specify com.ibm.ejs.am.mode.workbased in the Name field, and specify true in the Value field.
  4. Click OK to save the configuration. When you restart the server, the Alarm Manager will operate in quiet mode.
com.ibm.websphere.deletejspclasses
Deletes JSP classes for all applications after those applications have been deleted or updated. By default, the value of this property is true.

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties page.
    Base configuration Servers > Application Servers >server1 > Process Definition > Servant > Java Virtual Machine > Custom Properties
    ND configuration System Administration > Node Agents > nodeagent > Process definition > Control > Java Virtual Machine > Custom Properties
  2. If the property is not present in the list, create a new property name.
  3. Enter com.ibm.websphere.deletejspclasses in the Name field, and specify false in the Value field.
com.ibm.websphere.deletejspclasses.delete
Deletes JSP classes for all applications after those applications have been deleted, but not after they have been updated. By default, the value of this property is true.

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties page.
    z/OS configuration System Administration > Node Agents > nodeagent > Process definition > Control > Java Virtual Machine > Custom Properties
  2. If the com.ibm.websphere.deletejspclasses.delete property is not present in the list, click New to create a new property name.
  3. Enter com.ibm.websphere.deletejspclasses.delete in the Name field, and specify false in the Value field.
com.ibm.websphere.deletejspclasses.update
Deletes JSP classes for all applications after those applications have been updated, but not after they have been deleted. By default, the value of this property is true.

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties panel.
    Base configuration Servers > Application Servers >server1 > Process Definition > Servant > Java Virtual Machine > Custom Properties
    ND configuration System Administration > Node Agents > nodeagent > Process definition > Control > Java Virtual Machine > Custom Properties
  2. If the com.ibm.websphere.deletejspclasses.update property is not present in the list, click New to create a new property name.
  3. Enter com.ibm.websphere.deletejspclasses.update in the Name field, and specify false in the Value field.

Applicability of the following list: [Version 5.0.2 and later][Version 5.0.1 and later]

jmx.async.timeout

Note: This property only applies to WebSphere Application Server for z/OS Versions 5.0.1 and 5.0.2. No other versions of the product support this property. Starting with WebSphere Application Server for z/OS Version 5.1.0, the function this property provides is integrated with Workload Manager (WLM), and thejmx.async.timeout property is not supported.

The jmx.async.timeout custom property is associated with the asynchronous JMX connector. By setting this property, you can override the default timeout of 180 seconds (three minutes), which allows you to more closely control the behavior of the asynchronous JMX connector. Note that the value for this property uses milliseconds, not seconds. See the example, below.

If the timeout value is too short, JMX operations may fail to complete. If the timeout value is too long, JMX operations that take a long time to complete (for instance, because of a slow servant, lengthy MBean implementation, or server error) may slow down JMX clients.

The jmx.async.timeout property value is calculated in milliseconds, not seconds. The following example, shows 300000 milliseconds being specified, which equals 5 minutes:

<systemProperties xmi : id="Property_1106058358728" name="jmx.async.timeout" value="300000" description="5 minute timeout." required="false"/>

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties page:

    For a Base Server configuration with no Network Deployment manager, use the following administrative console path: Servers > Application Servers >server1 > Custom Properties

    For a Base Server with a Network Deployment manager, use the following administrative console path: System Administration > Deployment Manager > Process Definition > Control > Java Virtual Machine > Custom Properties.

  2. If the jmx.async.timeout property is not present in the list, click New to create a new property name.
  3. Enter jmx.async.timeout in the Name field, and specify an appropriate setting, in milliseconds, in the Value field.
invocationCacheSize

Specifies the size of the invocation cache that is used to store active URLs.

Steps for this task

  1. If the invocationCacheSize property is not present in the list, click New to create a new property
  2. Enter invocationCacheSize in the Name field, and your new setting for this property in the Value field. You can specify any number higher than 0 for the cache size. Setting the value to zero disables the invocation cache.
com.ibm.websphere.management.monitoring.pingInterval
Specifies, in seconds, how frequently the deployment manager checks to see if the node agent is still running. When this property is set for the node agent, it determines how frequently the node agent checks to see if the deployment manager is still running. When it is set for an application server, it determines how frequently the application server checks to see if the node agent is still running. .

The default value is 60 seconds. This value can be changed through the administrative console. However, it is not recommended that you change this default value unless you need to minimize the number of DNS lookups that occur.

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties page:

    For a Base Server configuration with no Network Deployment manager, use the following administrative console path: Servers > Application Servers >server1 > Custom Properties

    For a Base Server with a Network Deployment manager, use the following administrative console path: System Administration > Deployment Manager > Process Definition > Control > Java Virtual Machine > Custom Properties.

  2. If the com.ibm.websphere.management.monitoring.pingInterval property is not present in the list, click New to create a new property.
  3. Enter com.ibm.websphere.management.monitoring.pingInterval in the Name field, and specify an appropriate setting, in seconds, in the Value field.
com.ibm.ws.management.application.appDeploymentReuse
Specifies, whether or not some application configuration values are retained by the application update function and propagated to the new deployment.xml configuration file whenever you click Update on the administrative console Application Configuration page. To navigate to the Application Configuration page for a particular application, click Enterprise Applications > application_name.

By default, some application configuration settings, such as starting weight, classloader mode, shared libraries, and settings that can only be set on the Application Configuration page, revert to default values whenever you click Update on the Application Configuration page for that application. If you want the application update function to retain your previous settings and propagate them to the new deployment.xml configuration file, you must set the com.ibm.ws.management.application.appDeploymentReuse JVM custom property to true.

The default value is false

Steps for this task

  1. Connect to the administrative console and navigate to the Java Virtual Machine Custom Properties page:

    For a Base Server configuration with no Network Deployment manager, use the following administrative console path: Servers > Application Servers >server1 > Custom Properties

    For a Base Server with a Network Deployment manager, use the following administrative console path: System Administration > Deployment Manager > Process Definition > Control > Java Virtual Machine > Custom Properties.

  2. If the com.ibm.ws.management.application.appDeploymentReuse property is not present in the list, click New to create a new property.
  3. Enter com.ibm.ws.management.application.appDeploymentReuse in the Name field, and specify true in the value field.

Related tasks
Using the JVM
Custom property settings



Searchable topic ID:   xrun_jvm
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/xrun_jvm.html

Library | Support | Terms of Use | Feedback