In the WebSphere Application Server administrative console, you can change the values of the following custom JVM properties:
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
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
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 |
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. |
Steps for this task
Steps for this task
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 |
Steps for this task
z/OS configuration | System Administration > Node Agents > nodeagent > Process definition > Control > Java Virtual Machine > Custom Properties |
Steps for this task
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 |
Applicability of the following list: [Version 5.0.2 and later][Version 5.0.1 and later]
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
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.
Specifies the size of the invocation cache that is used to store active URLs.
Steps for this task
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
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.
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
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.