+

Search Tips   |   Advanced Search

Java virtual machine custom properties

Use the administrative console to change the values of JVM custom properties. To set custom properties, connect to the administrative console and navigate to the appropriate Java virtual machine custom properties page.

If the custom property is not present in the list of already defined custom properties, create a new property, and enter the property name in the Name field and a valid value in the Value field. Restart the server to complete our changes.

Use the Custom properties page to define the following properties for use by the Java virtual machine.


allowDeployerRoleGenPluginCfg

Set true to enable users with the deployer role to generate and configure the plugin-cfg.xml file. After we set and save this custom property, restart the application server.

If the custom property is missing or its value is set to false, the following situations occur when the user has the deployer role permissions:

To disable this function, delete the custom property or set its value to false.

Also, we can set this custom property from the command line that uses the wsadmin tool and the following Jacl script:

Usage:


com.ibm.cacheLocalHost

Set to true to instruct the IBM SDK for Java to cache the IP address returned from java/net/InetAddress.getLocalHost for the life of the JVM. This is a performance enhancement that is advised on all processes if the localhost address of a process does not change while it is running.

The address for servers configured using DHCP change over time. Do not set this property unless we are using statically assigned IP addresses for the server.


com.ibm.apc.nodeMMTimeout

When we set a node into maintenance mode and APC is set to automatic, by default, the deployment manager will time out the maintenance mode operation after 20 minutes. This can be changed by setting the generic JVM argument -DnodeMMTimeout on the deployment manager and restarting the deployment manager. For example, we could set -DnodeMMTimeout to 60 to allot 60 minutes before the maintenance mode operation is timed out. Relatedly, apcConcurrentStartSize may help in reducing the time that it takes for APC to handle the maintenance mode operation, and other considerations such as min != max on the dynamic cluster may reduce the chances that APC needs to make changes.


com.ibm.config.allow.set.session.timeout

Set this custom property to revert the behavior of PI20040 as it applies to the web.xml element session-timeout.

Leave this custom property unset to obtain the updated behavior provided by PI20040.

The default behavior is to obtain the updated behavior of PI20040. The updated behavior is correct according to the Servlet specification, and is the new default behavior when writing session-timeout. values. The custom property is provided to re-enable the prior behavior.


com.ibm.config.eclipse.wtp.enablejemtrim

Enable the pruning of intermediate DOM nodes after the XML parse of the metadata occurs for an application.

The setting for this property should match the setting for the com.ibm.config.eclipse.wtp.enablexmltrim custom property. Either both of these properties should remain unset, set to false, or set to tru.

The default is false.


com.ibm.config.eclipse.wtp.enablexmltrim

Enable the sharing of JavaClass instances, and the conversion of expanded JavaClass and JavaMethod objects to lightweight proxies after they are used.

The setting for this property should match the setting for the com.ibm.config.eclipse.wtp.enablejemtrim custom property. Either both of these properties should remain unset, set to false, or set to true.

The default is false.


com.ibm.config.eclipse.wtp.jem=finer

Generate a trace from code areas enabled when the com.ibm.config.eclipse.wtp.enablejemtrim custom property is set to true.

This property might impact performance. Therefore, this property should only be specified if a problem occurs during the pruning of intermediate DOM nodes after the XML parse of the metadata occurs for an application, and we need to obtain additional information to diagnose the cause of that problem.


com.ibm.config.eclipse.wtp.xmltrim=finer

Generate a trace from code areas enabled when the com.ibm.config.eclipse.wtp.enablexmltrim custom property is set to true.

This property might impact performance. Therefore, this property should only be specified if a problem occurs with the sharing of JavaClass instances, or the conversion of expanded JavaClass and JavaMethod objects to lightweight proxies after they are used, and we need to obtain additional information to diagnose the cause of that problem.


com.ibm.disableCommonsElCache

Set to true to disable the commons-el expression cache if we are experiencing out of memory conditions because the hash maps are held by the expression evaluator.

The default is false.

com.ibm.eclipse.wtp.allowRootedEntries

In previous service releases, properties files in the root directory of an enterprise archive (EAR) file are not read properly. Thus, in this service release and later, the behavior is changed so that the class path in META-INF and MANIFEST.MF files are treated as a relative URI. To revert to the original behavior, set the com.ibm.eclipse.wtp.allowRootedEntries to true.


com.ibm.ejs.ras.disablerasnotifications

Disable and enable RAS service. When true, RAS services are disabled. The default value for this property is false.


com.ibm.ejs.ras.writeSystemStreamsDirectlyToFile

Support JSR-47 customized logging to write to the SystemOut stream without the format of WebSphere Application Server. The format of WAS includes information, for example, timestamp, thread ID, and some others. An application might not want this information to appear in the SystemOut stream (or perhaps prefer the information to appear in a different format). To disable the format of WAS, set this custom property to true.


com.ibm.ejs.sm.server.quiesceInactiveRequestTime

Specify, in milliseconds, how fast IIOP requests through the Object Request Broker (ORB) can be received and processed. For example, if we specify a value of 5000 for this property, the server does not attempt to shut down until incoming requests are spaced at least 5 seconds apart. If the value specified for this property is too large, when the application server is stopped from the administrative console the following error message might be issued:

The default is 5000 (5 seconds).

If we decide to use this custom property, we can specify it as a JVM custom property for either an application server, a node agent, or a deployment manager. It is typically set as an application server JVM custom property.


com.ibm.ejs.sm.server.quiesceTimeout

Specify, in seconds, the overall length of the quiesce timeout. If a request is still outstanding after this number of seconds, the server might start to shut down. For example, a value of 180 would be 3 minutes. If the quiesce time is exceeded, the workload regulator rejects all incoming requests and server shutdown occurs.

The WTRN0036W message is issued when outstanding transactions exist while server is in the quiesce state.

The default is 180.

If the timeout value is set to zero the quiesce function is disabled.

If we decide to use this custom property, we can specify it as a JVM custom property for either an application server, a node agent, or a deployment manager. It is typically set as an application server JVM custom property.


com.ibm.ffdc.log

Specify where to store first failure data capture (FFDC) data when a failure occurs during product runtime processing. The FFDC feature instantly collects information about the events and errors that lead up to the failure. The captured data can then be used to analyze the problem. After the information is collected, and saved in a log file, FFDC returns control to the affected engines.

Example of use, specifying a folder location for the log file:

Example of use, specifying an actual file name for the log file:


com.ibm.websphere.application.updateapponcluster.waitforappsave

Specify, in seconds, the amount of time that we want the deployment manager to wait for the extension tasks of the save operation to complete before it starts the updated application.

This property is only valid if it is specified for a deployment manager.

Usually during the save operation for an application update being used performed using the rollout update process, the extension tasks of the save operation run as a background operation in a separate thread. If the main thread of the save operation completes before the synchronization portion of the rollout update process, the updated application fails to start properly.

When we add this custom property to the deployment manager settings, if the extension tasks of the save operation do not complete within the specified amount of time, the rollout update process stops the application update process, preventing the application from becoming corrupted during the synchronization portion of the rollout update process.

The default is 180.


(ZOS) com.ibm.websphere.bean.delete.sleep.time

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 enterprise bean container.

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

com.ibm.websphere.collective.utility.autoAcceptCertificates

To automatically trust SSL (Secure Sockets Layer) certificates, set this property to true.


com.ibm.websphere.deletejspclasses

Delete JavaServer Pages classes for all applications after those applications are deleted or updated. The default is false.

In a Network Deployment environment, this property applies to the WebSphere Application Server.

Set this property on a node agent when the application server runs in a federated cell.


com.ibm.websphere.deletejspclasses.delete

Delete JavaServer Pages classes for all applications after those applications are deleted, but not after they are updated. The default is false.

In a Network Deployment environment, this property applies to the WebSphere Application Server.

Set this property on a node agent when the application server runs in a federated cell.


com.ibm.websphere.deletejspclasses.update

Delete JavaServer Pages classes for all applications after those applications are updated, but not after they are deleted. The default is false.

In a Network Deployment environment, this property applies to the WebSphere Application Server.

Set this property on a node agent when the application server runs in a federated cell.


com.ibm.websphere.ejb.UseEJB61FEPScanPolicy

Control whether the product scans pre-Java EE 5 modules for more metadata during the application installation process or during server startup. By default, these legacy EJB modules are not scanned.

The default is false.

We must set this property to true for each server and administrative server that requires a change in the default value.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.ejbcontainer.expandCMPCFJNDIName

The EJB container should allow for the expansion of the CMP Connection Factory JNDI Name when a user's JNDI name contains a user-defined Application Server variable. The custom property, com.ibm.websphere.ejbcontainer.expandCMPCFJNDIName, makes it possible to expand the CMP Connection Factory JNDI Name.

If the value is true, which is the default, the EJB Container expands a variable when found in the CMP Connection Factory JNDI Name. If the value is set to false, the EJB Container does not expand a variable.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.ejbcontainer.includeRootExceptionOnRollback

Use this EJB custom property to enable the following functions:

To enable this function, set this property to true. To disable this function, set this property to false.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.jaxrpc.stub.typemapping.per.thread

Indicate whether the JAX-RPC runtime should use thread specific type mapping objects.

The JAX-RPC runtime uses a single TypeMappingRegistry object for all of the JAX-RPC clients. This design is intentional, and allows us to create a JAX-RPC stub and use it on multiple threads. However, the singleton TypeMappingRegistry gets contaminated if multiple JAX-RPC Web services with different mappings are invoked concurrently. Even though this situation is uncommon, if it exists on the system, we can set the com.ibm.websphere.jaxrpc.stub.typemapping.per.thread custom property to true to indicate to the JAX-RPC runtime that it can use thread-specific type mapping objects. These separate mapping objects avoid the contamination issue, and the various web service calls will succeed.

The default is false.

We should not use this custom property unless we encounter a situation where the singleton TypeMappingRegistry gets contaminated. Enabling this property might regress applications that depend on access to the same JAX-RPC stub across multiple threads.


com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine

Disable the JAX-RS integration run time from automatically processing the JAX-RS applications. The default is false.

When true also disables the IBM JAX-RS runtime integration with EJB and JCDI.


com.ibm.websphere.logging.useJULThreadID

Control thread ID type used in WAS log files.

When true, LogRecord instances are used to retrieve thread ID. When false, Thread instances are used to retrieve thread ID.

The default is false.

For transitioning users: Beginning with v8.5, the default value for this property is false. In earlier versions, the default value for the com.ibm.websphere.logging.useJULThreadID property is true.trns


com.ibm.websphere.management.application.client.EnvEntry_processBindings

Specify how an environment entry value is handled during an application deployment.

If false, an environment entry value is read from, and written to, the deployment descriptor. Any environment entry value specified in the XML bindings is ignored.

If not specified, or has a value of true, an environment entry value that is specified in the XML bindings is given preference over the value specified in the deployment descriptor. The environment entries from annotations are processed. Default is true.

If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a pre-v8.0 environment, the environment entry value in the XML bindings is not recognized by both the deployment and runtime environments.

If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a v8.0 or later environment, the environment entry value in XML bindings are not recognized by the deployment environment but are recognized by the runtime environment.

Do not include the com.ibm.websphere.management.application.client.EnvEntry_processAnnotations custom property in the JVM configuration settings if the com.ibm.websphere.management.application.client.EnvEntry_processBindings custom property is set to true.

If the environment contains pre-v8.0 nodes and an application is targeted to a pre-v8.0 node, set this property with a value of false if we have an environment entry defined in the application and the environment entry value is going to be provided or changed during deployment including install, edit, or update. Otherwise, the application deployment fails.


com.ibm.websphere.management.application.fullupdate

Specify that when any of the applications are updated, we want the binaries directory erased and the content of the updated EAR file completely extracted.

If not specified, each changed file within an updated EAR file is individually updated and synchronized in the node. This process can be time consuming for large applications if many files change.

Set the com.ibm.websphere.management.application.fullupdate property to:


com.ibm.websphere.management.application.fullupdate.application_name

Specify that when the specified application is updated, we want the binaries directory for that application erased and the content of the updated EAR file completely extracted.

If not specified, each changed file within the updated EAR file for the specified application is individually updated and synchronized in the node. This process can be time consuming for large applications if many files change.

Set the com.ibm.websphere.management.application.fullupdate.application_name property to:


com.ibm.websphere.management.application.keepExistingSharedLibraries

Specify how shared library mappings are handled during application updates.

When false, then the shared libraries that are specified during the application update operation should replace the original shared library settings. False is the default setting.

When true, after an application is updated, the application and module configurations include the original shared library settings in addition to those specified during the update operation.


com.ibm.websphere.management.application.persistWebContext

Specify whether the context root and virtual host information for web modules is persisted in the deployment.xml file. If not specified, application deployment has to rely on annotation processing to read the context root and virtual host information, which impacts the performance of application deployment

When true, the context root and virtual host information for web modules is persisted in the deployment.xml file, the persisted data is used for application deployment validation, which improves the performance of application deployment.

The default is false, which means that the context root and virtual host information for web modules is not persisted in the deployment.xml file.


com.ibm.websphere.management.application.sync.recycleappasv5

Specify that we want the application recycling behavior to work the same way as this behavior worked in versions previous to v6.x of the product.

In v6.x and higher, after an application update or edit operation occurs, depending on which files are modified, either the application or its modules are automatically recycled. This recycling process occurs for all application configuration file changes, and all non-static file changes.

However, in versions previous to v6.x of the product, an application is recycled only if the Enterprise Archive (EAR) file itself is updated, or if the binaries URL attribute changes. An application is not recycled if there is a change to the application configuration file.

Set the com.ibm.websphere.management.application.sync.recycleappasv5 property to:

The default is false.

Define this property in the node agent JVM. However, when defining this property, we can specify a scope of cell if we want the setting to apply to all of the nodes within a specific cell. If this property is set at both the cell and node agent level, the node agent setting takes precedence for that particular node agent.


com.ibm.websphere.management.application.updateClusterTask.serverStopWaitTimeout

Specify, in seconds how long the deployment manager waits for a server to stop completely in the $AdminTask updateAppOnCluster task. By default, the deployment manager waits for 600 seconds. The amount of time specified for this property should be greater than the longest amount of time that it takes to stop a server in the cluster.

This property can only be specified if we are using v7.0.0.1 or higher.

This property is only valid if it is specified for a deployment manager.


com.ibm.websphere.management.application.updatesync.appExpansionTimeout

Specify how long the deployment manager waits to start an application server following an application update. This wait time enables the binaries for the application to be expanded to their directories after the update process completes. The amount of time specified for this property should be the maximum amount of time any of the applications that reside in a node, take to fully expand their binaries.

By default, the rollout update function waits for 60 seconds, for each application expansion to occur following an update to one or more applications. Because the rollout function can be used to update multiple applications at the same time, the default value for this property is n x 60 seconds, where n is the number of applications that are being updated.

The default wait time might not be sufficient for larger applications. If after the applications are updated one or more of these applications do not start when the server starts, we might have to specify a longer length of time for the rollout update function to wait before starting the server.

This property is only valid if it is specified for a deployment manager.


com.ibm.websphere.management.configservice.getServerLogRootFromTemplate

Specify whether the value specified for the SERVER_ROOT variable defined in a server template, or the value of {LOG_ROOT}/serverName should be used when you create an application server or cluster member.

When we create an application server or cluster member, the value of {LOG_ROOT}/serverName is always used instead of the value of theSERVER_ROOT variable defined in an existing server template. If, when you create an application server or cluster member, we want to use the value of the SERVER_ROOT variable defined in a server template, set this property to true.

If we use this custom property, it must be set for the deployment manager.

When using wsadmin in connected mode, use the AdminTask.setJVMSystemProperties command to set this property at the deployment manager level.

When using wsadmin in LOCAL mode (conntype=none), this property can be passed in as a javaoption:


com.ibm.websphere.management.configservice.sessionIdUniqueness

Prevent duplicated configuration session or workspace ID generation. If different processes create randomly generated configuration session or workspace IDs within the same millisecond, it is possible for the IDs to be identical.

To prevent duplicated configuration session or workspace ID generation, add this property to the application server settings and set it to true.

Use either the AdminTask.setJVMSystemProperties wsadmin command or the administrative console to specify this custom property.

If the application server is part of a federated cell, after you save the changes, we must synchronize the node, and restart each server before this configuration change goes into effect.

If we decide to use this custom property, we can specify it as either a deployment manager or an application server JVM custom property.


com.ibm.websphere.management.configservice.validatePropNames

Enforce character restrictions for custom property names, and for the name value of Property and J2EEResourceProperty configuration objects in wsadmin commands.

Using one of the following methods to turn off character validation for custom property names, and the name value of Property and J2EEResourceProperty configuration objects in wsadmin commands.


(ZOS) com.ibm.websphere.management.jmx.random

Enable the controller to randomly select an initial servant from the servant pool to process a JMX connector requests instead of automatically assigning the request to the hot servant.

By default, when multiple servants are enabled and the application server receives a JMX connection request, the application server assigns the request to the first servant, which is also referred to as the hot servant. This strategy minimizes the risk that the request is assigned to a servant that is paged out. However, if the first servant has a heavy workload, requests to that servant eventually fail. Therefore, the advantage of using the random algorithm is that the assigned servant is probably not already handling many other requests. The disadvantage of using the random algorithm is that the selected servant might be paged out and have to be paged back in before it can handle the request.

Set the com.ibm.websphere.management.jmx.random property to:

If we decide to use this custom property, specify it as a JVM custom property for the controller.


com.ibm.websphere.management.nodeagent.bootstrap.maxthreadpool

Control the number of threads that can be included in a newly created thread pool. A dedicated thread is created to start each application server JVM. The JVMs with dedicated threads in this thread pool are the JVMs that are started in parallel whenever the node agent starts.

We can specify an integer from 0 - 5 as the value for this property. If the value we specify is greater than 0, a thread pool is created with that value as the maximum number of threads that can be included in this newly created thread pool. The following table lists the supported values for this custom property and their effect.

com.ibm.websphere.management.nodeagent.bootstrap.maxthreadpool Effect
0 or not specified The node agent starts up to five JVMs in parallel.
1 The node agent starts the JVMs serially
Integer value between 2 and 5 The node agent starts a number of JVMs equal to the specified value in parallel.

For example, suppose the node agent has 10 JVMs that are set as running state, which means they are started whenever the node agent starts. If we specify 3 for this property, whenever you stop and start the node agent, only three of the 10 JVMs are started in parallel when the node agent starts.

This property is not specified by default. If we decide to use this custom property, we must specify it as a node agent JVM custom property.


com.ibm.websphere.management.nodesync.skipWebServerTarget

Control whether application binaries are distributed to target nodes in which the application only targets web servers.

By default, the custom property value is set to false, which causes the application server to distribute application binaries to target nodes. If we set this custom property to true, the application server does not distribute application binaries to target nodes that contain web server targets only.

Important: System behavior is not affected by this custom property value. Also, it is not affected by the node synchronization change that led to a change in this custom property value for target nodes that contain application server targets. These statements are true regardless of whether web server targets are included in that same node.

The following sample output shows the isAppReady output, which is generated for web server-only target nodes when we set this custom property to true:

We can set this custom property for the deployment manager, but not the application server or node agent. Use the administrative console or complete the following steps using a command-line:

  1. Start the wsadmin scripting tooling from the profile_root/bin directory. We need to start the .wsadmin.bat or wsadmin.sh command within that directory.

  2. Run one of the following commands:

    Use Jacl

    $AdminTask setJVMSystemProperties {-serverName server -nodeName node -propertyName com.ibm.websphere.management.nodesync.skipWebServerTarget -propertyValue true}

    Use Jython string

    AdminTask.setJVMSystemProperties('[-serverName server -nodeName node -propertyName com.ibm.websphere.management.nodesync.skipWebServerTarget -propertyValue true]')

    Use Jython list

    AdminTask.setJVMSystemProperties (['-serverName', 'server', '-nodeName', 'node' '-propertyName', 'com.ibm.websphere.management.nodesync.skipWebServerTarget', '-propertyValue', 'true'])

    where the server and node variables are specific to the environment.

  3. Restart the deployment manager.


com.ibm.websphere.management.processEmbeddedConfigGlobal

Globally enable or disable processing of the embedded configuration of enhanced application Enterprise Archive (EAR) files during deployment. An enhanced EAR file results when you export an installed application.

This custom property overrides globally the default setting for the Process embedded configuration (-processEmbededConfig) option. By default, Process embedded configuration is set to true (selected) for enhanced EAR files and false (deselected) for all other EAR files. The Process embedded configuration setting determines the directory to which the product expands an enhanced EAR file during deployment of the enhanced EAR file. If we exported an application from a cell other than the current cell and did not specify the $(CELL) variable for Directory to install application when first installing the application, setting Process embedded configuration to false during deployment of an enhanced EAR file extracts the enhanced EAR file in the app_server_root/profiles/installedApps/current_cell directory. Otherwise, if Process embedded configuration is set to true, the enhanced EAR file is expanded in the app_server_root/profiles/installedApps/original_cell directory, where original_cell is the cell on which the application was first installed. If we specified the $(CELL) variable for Directory to install application when we first installed the application, installation expands the enhanced EAR file in the app_server_root/profiles/installedApps/current_cell directory.

When this processEmbeddedConfigGlobal custom property is set to false, the product does not process the embedded configuration of any application, including enhanced EAR files, during deployment. After we set processEmbeddedConfigGlobal to false, the product does not process the embedded configuration of enhanced EAR files. However, when deploying an individual enhanced EAR file, we can override this false setting by explicitly setting Process embedded configuration to true.

When this processEmbeddedConfigGlobal custom property is set to true, the product processes the embedded configuration of enhanced EAR files.

Regardless of whether this processEmbeddedConfigGlobal custom property is set to true or false, the product deploys applications that do not have embedded configurations as usual. The setting has no effect on deployment.

If we decide to use this custom property, we must either specify this property and its value as a JVM custom property for both the Control and Servant, or add this property to the wsadmin.properties file.

If we decide to use this custom property, we must either specify this property as a JVM custom property for the deployment manager, or add this property to the wsadmin.properties file.


(ZOS) com.ibm.websphere.management.registerServerIORWithLSD

Control whether a federated server registers with the Location Service Daemon (LSD). Normally, a federated server requires the node agent to be running. To direct the server to not register with the LSD and remove its dependency on an active node agent, the com.ibm.websphere.management.registerServerIORWithLSD JVM custom property must be set to false, and the ORB_LISTENER_ADDRESS must be set to a value greater than 0 so that the ORB listens at a fixed port. The setting for this property is ignored if the ORB_LISTENER_ADDRESS property is set to 0 (zero) or is not specified, and the federated server registers with the LSD.

Set to false to have server to run even when the node agent is not running. When true, the federated server registers with the LSD. Default is true.

This property already exists in the list of ORB Service custom properties. To change the setting for this custom property, in the administrative console, click...

        Servers > Application Servers > server > session management > Container Services > ORB Service > Custom Properties > com.ibm.websphere.management.registerServerIORWithLS.

After we change the value for this custom property, we must do a full synchronization before this change is reflected in the server.xml file on the node. If we cannot start the node agent for the server, we must manually edit the server.xml file to change the value of this custom property from true to false.

When we set the com.ibm.websphere.management.registerServerIORWithLSD property to false, the server does not notify the node agent when it dynamically assigns the ORB_LISTENER_ADDRESS port. There also will not be any indirect Interoperable Object References (IORs) that the node agent can resolve to a server. All of the IORs become direct, which means that the node agent can only contact that server if a static ORB_LISTENER_ADDRESS has been assigned to that server.

If we set the com.ibm.websphere.management.registerServerIORWithLSD property to false and do not intend to use the high availability manager (HAManager) service and node agent process, then we should create a static routing table to enable static routing. Enabling static routing ensures that workload management (WLM) continues to function properly. We use com.ibm.websphere.management.registerServerIORWithLSD to prevent indirect IORs from being returned for any services being provided by the application servers (and having the node agent then map these indirect IORs to direct IORs).

The use of the node agent establishes a known port on the server side to which the client can send requests when the ports for the application servers are not known. Creating a static routing table and enabling static routing provides static ports for the application servers and make these ports available for use. With static ports, node agent processing is not necessary.

With dynamic application server ports, we cannot use the static routing table. Node agent processing is required with dynamic application server ports because the client needs to obtain the new port information when the servers are restarted.

Set the com.ibm.websphere.management.registerServerIORWithLSD property does not affect the use of either dynamic or static ports or the routing of requests by WLM. However, we do lose a potential level of failover provided by the node agents of the HAManager.

WLM processing is retained with weighted spraying of requests.


com.ibm.websphere.management.soapSocketConnectionTimeout

Specify, in seconds, how long a JMX SOAP connector socket should remain open. If we do not specify a value for this property, the JMX SOAP connector socket connection stays open indefinitely.


com.ibm.websphere.management.useUpdatedPropertyFiles

Create new mail sessions using the updated properties file template.

Set to true to use the updated properties file configuration template to create new mail sessions. The updated properties file configuration template will be used instead of the original properties file configuration template.

We should enable com.ibm.websphere.management.useUpdatedPropertyFiles unless we used the original properties file template to extract WAS configuration objects to the property files.bprac

After we set the system property, save the changes. If the application server is part of a federated cell, synchronize the node to propagate the changes. Restart each server for the changes to take effect.

This property is not enabled by default.


com.ibm.websphere.metadata.ignoreDuplicateRefBindingsInWebModules

Control whether the JVM ignores instances of duplicate reference bindings in the DTD file for a web module in a J2EE version 1.3 application. Typically a MetaDataException occurs if the DTD file for a web module in a J2EE version 1.3 application contains duplicate references.

The standards for the DTD file for a web module specifically state that the reference bindings must have a unique name fields. Therefore, an application containing a web module that includes duplicate reference bindings is technically a non-compliant application.

Although the standards for the DTD file for a web module forbid a user from defining duplicate reference bindings, the JVMs in versions of the product that preceded 7.0 tolerate duplicate reference bindings. If we have DTD files for web modules in J2EE version 1.3 applications that contain duplicate reference bindings, we can either remove the duplicate reference, or add this property to the JVM configuration settings, and set the property to true.


com.ibm.websphere.network.useMultiHome

Use this property in a multihomed environment to indicate on which IP addresses the application server listens. In a multihomed environment, there is normally a specific IP address that the application server is restricted to listening on for Discovery and SOAP messages. Setting the com.ibm.websphere.network.useMultiHome property to:

(ZOS) In a multihomed environment where the product 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 and all node agents. 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, the product only listens for Discovery and SOAP messages on the configured host name. If we set the property to false, we must also:

We 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, we must restart the server.

If we cannot contact the server, check the setting for com.ibm.websphere.network.useMultihome to ensure that it is correct. We can change the value through the administrative console. Modify the defaults by setting the value for the server, deployment manager, and node agent. We must restart the server before these changes take effect.


com.ibm.websphere.perf.tuning.disableRPARepositoryCache

Prevent the caching of server configuration details when RPA is disabled.

RPA uses a repository cache to store the configuration details of the server. This cache is initialized and configuration details are stored even if RPA and PMI are disabled. The repository cache can become quite large for extremely large installations, such as an installation that has over 3000 datasources. If we encounter performance problems because of the size of this repository cache, and RPA is disabled, add this property to the JVM configuration settings and set it to true. We should not use this custom property if RPA is enabled, or if we are not encountering performance problems because of the size of this repository cache.

We should not use this custom property if RPA is enabled, or if we are not encountering performance problems because of the size of this repository cache.

The default value for this property is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.resource.xmlConfigMaxLineLength

Specify a preferred maximum line length for XML configuration documents.

Lines at the beginning of a server.xml file often exceed 2048 characters in length. Lines exceeding 2048 characters in length cannot be processed by common text editing tools on some operating systems, such as z/OS. Therefore, when you edit and save a file that includes lines exceeding 2048 characters, the long lines are truncated. This truncation makes the configuration file unusable, and causes the server startup to fail.

If we specify a value for this property, when you edit and save an XML configuration document, the line breaks will occur as soon as possible after the number of characters in the line reaches the specified maximum number of allowable characters. The line breaks still occur at logical breaking points, which is why the line lengths might still exceed the specified maximum. Therefore, the value we specify for this property should take into account the number of characters that might exceed the specified maximum to ensure that none of the lines in the document exceed 2048 characters.

If we do not specify a value for this property, lines are allowed to grow to any length.

An acceptable value for this property is an integer in the range 80 to 2046, inclusive.

There is no default value for this property.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.security.ltpa.disableSECJ0371W

Disable the logging of message SECJ0371W.

The SECJ0371W message indicates that the token has expired. Although these messages can be helpful, we might want to disable them, if they are a nuisance. In some environments, these messages can litter logs, which makes it harder to find other error messages and conditions. See the SECJ0371W message for more information.


com.ibm.websphere.sib.webservices.useTypeSoapArray

We can pass messages directly to a bus destination by overriding the JAX-RPC client binding namespace and endpoint address. However:

Here are examples of the two different messages:

Set to true to modify the default behavior and send a string array message that is fully compatible with standard JAX-RPC. Setting this property modifies the default behavior for all outbound JMS web services invocations sent from the service integration bus.


com.ibm.websphere.webservices.attachment.tempfile.expiration

Indicate, in seconds, an expiration time for an attachment on a JAX-WS or Service Component Architecture (SCA) client or service. If an attachment is not accessed for a period of time greater than the expiration time, the web service runtime is allowed to delete the attachment.

The JAX-RPC programming model allows access to attachments from incoming web service messages. The attachment might be accessed immediately, or might be stored for later processing. Therefore, the memory associated with the attachment might persist much longer than the lifetime of the web service interaction because there is no precise length of time after which the web service runtime can safely free the attachment.

For small attachments, the memory is eventually freed by the Java garbage collector.

For large attachments, the JAX-RPC runtime stores the attachment data in a temporary file, thereby allowing the runtime to process extremely large attachments without consuming memory. If the application does not access the attachment, or if the application does not adequately close the data handler associated with the attachment, the large temporary file is not freed. Over time, these temporary attachment files might accumulate on the file system if no expiration time is specified for these files.

A setting of 600 is recommended if we need to specify an expiration time for these attachments. The default setting for this custom property is 0 seconds, which indicates that there is no expiration time for these attachments.bprac

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.attachements.maxMemCacheSize

Specify, in kilobytes, the maximum size of an attachment on the JAX-RPC client or service that can be written to memory. For example, if the web service needs to send 20 B attachments, set the property to 20480.

When determining a value for this property, remember that the larger the maximum cache size, the more impact there is on performance, and, potentially, to the Java heap.

If we do not specify a value for this property, the maximum memory used to cache attachments is 32 KB, which is the default value for this property.

To specify the maximum size of an attachment on the JAX-WS client or service, see the com.ibm.ws.websvcs.attachments.sizethreshold custom property.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.DisableIBMJAXWSEngine

Turn off web services annotation scanning at the server level. By default, web services annotation scanning is enabled at the server level.

To turn off annotation scanning at the application level, set the DisableIBMJAXWSEngine property in the META-INF/MANIFEST.MF of a WAR file or EJB module to true.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.http.OneWayConnectionRecycleTime

Specify, in seconds, how long the web services engine should wait before reusing a one-way connection. When a one-way connection is reused too quickly, a web service operation might fail on the client because of a timeout problem, such as a SocketTimeoutException.

When a value is specified for this property, one-way connections are not reset until the specified number of seconds elapses, starting from when the request is sent.

By default, this property is not set and one-way connections are reset immediately after the request is sent.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.http.waitingThreadsThreshold

Specify how many waiting connection requests are tolerated before releasing soft connections. A soft connection occurs when a client engine maintains connection objects for some hosts after the connection is closed. By default, after five threads are waiting for connections, the client engine releases the soft connections.

If all of the connections are being used, the custom property does not have an impact. In this situation, we can increase the maximum connection limit, the maximum number of threads, or both.

The default value for this custom property is 5.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.jaxrpc.client.publishwsdl

Specifies whether a WSDL file is published for a client web module. When true, if an application contains a client web module, a WSDL file might be published for that client. If we do not want WSDL files published for our client applications, set this property to false.

Default is true.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.management.connector.http.header.includeProductVersion

Set this to a value of true to include server version information in the SOAP port HTTP response header. The default is false.


com.ibm.websphere.webservices.jaxws.setLinkValuePrecedence

Precedence of link values in the JAX-WS runtime environment.

When true, deployment descriptor link values have precedence over annotation link values.

The default is false.


com.ibm.websphere.webservices.soap.enable.legacy.get.behavior

Starting in WAS v8, the SOAPMessage.getSOAPHeader and getSOAPBody methods throw a SOAPException if there is no corresponding element in the message. A system property, com.ibm.websphere.webservices.soap.IBMSOAPMessage.ENABLE_LEGACY_GETSOAP_BEHAVIOR, is provided to revert the behavior to return null rather than throw an exception. This system property is set using a JVM custom property, com.ibm.websphere.webservices.soap.enable.legacy.get.behavior. The default value for this JVM custom property is false. Setting this JVM property to true reverts to the previous behavior, which is to return a null for SOAPMessage.getSOAPHeader and getSOAPBody methods when there is no corresponding message.

The previous behavior of returning null is not compliant with the specification.


com.ibm.websphere.webservices.tempAttachDir

Specify the location on a storage device where we want the web services runtime to cache a copy of any attachment that is greater than 32 KB and sent or received as part of a SOAP message.

For performance reasons, the web services runtime caches a temporary copy of any SOAP message attachment that is greater than 32 KB. If we do not specify a value for this property, the cached copy of the attachment is typically sent to the default temporary directory for our operating system.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.transport.jms.messageType

Control the JMS message type used by the web services engine for SOAP over JMS components when sending request and response messages. To specify a JMS BytesMessage (javax.jms.BytesMessage) object, set the property to BYTES to indicate that the body of the message is binary data. To specify a JMS TextMessage (javax.jms.TextMessage) object, set the property to TEXT to indicate that the body of the message is string data.

The default value for this custom property is BYTES.

To learn more about the SOAP over JMS message types, see the configuring SOAP over JMS message types information.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.transport.OPTIMIZE_HTTP_HEADERS

Prior to v8, a JAX-WS client application for WAS might send a SAVE_CONNECTION HTTP header in a SOAP message. This additional header ensures that proper processing occurs by the application server hosting the JAX-WS web service. However, this SAVE_CONNECTION header and the additional processing is not necessary if the application server for the client and the application server host for the web service are both using WAS v7.0 Fix Pack 3 or later.

We can set the com.ibm.websphere.webservices.transport.OPTIMIZE_HTTP_HEADERS custom property to false to enable the SAVE_CONNECTION header to ensure proper processing by older application server levels. By default, this custom property is set to true, which disables the JAX-WS client from sending the SAVE_CONNECTION header. To change this default behavior, set the custom property to false on the application server hosting the JAX-WS client application.

Important: We must verify that the application server for the client and application server host for the web service are both using v7.0 Fix Pack 3 or later.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.transport.ssl.loadFromPolicyBinding

Control whether JAX-WS applications use SSL transport bindings or the system default SSL settings when the client is a managed client, and the client and the server are in different application servers.

When we create an SSL binding, this property is automatically added to the bindings file, and set to true. This setting enables SSL transport bindings to be used for JAX-WS applications when the client is a managed client, and the client and the server are in different application servers. If no bindings are attached to the JAX-WS application, set this property to false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.UseWSFEP61ScanPolicy

Control whether the product scans WAR 2.4 and earlier modules for JAXWS components and semi-managed service clients. By default, these legacy WAR modules are only scans for semi-managed service clients.

The default is false.

We must set this property to true for each server and administrative server that requires a change in the default value.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.webservices.WSDL_Generation_Extra_ClassPath

Set the location of the shared class files. The wsgen command-line tool generates the necessary artifacts required for JAX-WS applications when they start from Java code. However, the wsgen command-line tool might not locate the necessary class files and append the following error messages to the log file:

Provide the fully qualified location to the missing class files. With this custom property, we should provide fully qualified paths to multiple Java archives (JAR) and separate them using a semicolon (;). (ZOS) To avoid trouble, set this property to all JVM processes, including deployment manager, node agent and application server.

If our base operating system for WAS is AIX, Linux, or UNIX, then use a colon (:) to separate the multiple Java archives (JAR) and directories.

Example: D:\sharedlibs;D:\libs\WSBean.jar

If we decide to use this custom property, specify it as an application server JVM custom property.

(ZOS) Remember: Set this property for both the controller and the servant. We can set this property for the servant as follows:

(ZOS) Avoid trouble: If to set this property on z/OS, set the property for both the Control and Servant JVM Custom Properties in the administrative console:


com.ibm.websphere.websvcs.EJBPostInvokeCallOnException

Clean up the state and transaction following an exception in a web-services-invoked EJB.

On installations of WAS that use JAX-WS web services, when an exception occurs in an EJB that is invoked as part of a web service, transactions could remain active on a thread and prevent a transaction associated with the current XA transaction flow from resuming. Set to true to ensure complete cleanup of the state and transaction.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.websphere.workspace.decodeclustervariable

Ensure that variables defined at a cluster scope are expanded when they occur in log file paths defined in the administrative console.

If this property is not set, and cluster scoped variables are used to define log file paths, then the deployment manage might fail to retrieve the requested log file. Therefore, we should add this property to the deployment manager JVM settings if you include cluster scoped variables in your log file paths.

The default is false.

If we decide to use this custom property, specify it as a deployment manager JVM custom property. After we set this property to true, we must restart the deployment manager before this change goes into effect.


com.ibm.websphere.wsrm.MaxSequenceBacklog

Configure the maximum number of messages on an outbound WS-RM sequence.

When the defined limit is reached, WS-RM will reject any new messages by throwing a javax.xml.ws.WebServiceException exception until the backlog decreases below the limit. Clients receiving an exception should retry the request.

There is no default value set. If no value set is defined, the backlog limit is infinite.


com.ibm.websphere.wsrm.MessageContextCacheSize

Set the maximum size of the in-memory cache to a positive integer value.

There is no default value set. The size of the cache is infinite.


com.ibm.websphere.wsrm.pollingInterval

Specify the frequency with which MakeConnection requests are made for a Sequence.

The value specifies the interval in milliseconds. The default behavior when the property is no set is 3000 milliseconds.


com.ibm.websphere.wsrm.retransmissionInterval

Specify the frequency with which WS-RM retransmits application messages when previous attempts to transmit the message have failed.

The value specifies the interval in milliseconds. The default behavior when the property is not set is 15000 milliseconds.


(ZOS) com.ibm.websphere.zos.userdir.useRacfSettings

When false, the user.dir is set by WAS code to ${USER_INSTALL_ROOT}, the part of the config filesystem path before the /profiles/ directory.

When true, the user.dir is not set by WAS code. Instead, the user.dir is set by allowing the USS settings to take effect (user.dir == OMVS segment home directory).

Since WAS is not setting the property, we can define user.dir in the servant JVM custom properties to a value of our choice. Once we have defined user.dir, Java code will set it via the options file servant.jvm.options.

Change the user.dir changes only the value of the property. It does not change the current working directory of the JVM, which is set at boot time.


com.ibm.ws.amm.require.produces.annotation.for.cdi

WAS incorrectly ignores the following annotations (@EJB, @WebServiceRef, @PersistenceContext, @PersistenceUnit, and @Resource) unless an @Produces annotation is present on the CDI bean. This behavior is incorrect since there is no Java EE requirement that the @Produces annotation be present. Since existing applications have dependencies on this incorrect behavior, the specification-incorrect behavior remains the default. This custom property is provided to allow us to obtain the specification-correct behavior by setting the property to false.

Set the property to false to obtain the specification-correct behavior when all of the following are true:


com.ibm.ws.amm.scan.context.filter.archives

Provide a list of archives, or utility JAR files, that do not contain annotations. Archives or utility JAR files specified for this property are not be scanned for annotations.

When a Java EE 5 or 6 application is deployed or updated, the Annotations Metadata Manager (AMM) facility scans all of the annotation metadata. This scanning process can negatively affect the amount of time required to deploy an application. If the application includes archives or utilities that do not contain annotations, we can list these archives and utilities as the value for this property. If the application includes Java Packages that do not contain annotations, we can list them as the value for the Ignore-Scanning-Packages property.

The values specified for these properties are case-sensitive, and must be expressed as a single string with a comma followed by a space used to separate the names of the archives or utility JAR files. Wildcards and REGEX expressions are not permitted.

As an alternative to using this custom property, we can add the Ignore-Scanning-Archives property to one of the following files or modules, and specify the archives and utilities that we do not want scanned as the value of that property:

Values specified in the amm.filter.properties files are merged with those found in this custom property to form a server scoped set of filters. This merged set of filters applies to all of the applications deployed on that server.

Values specified in the manifest file of an application are merged with the server scoped set of filters to form a module scoped superset that applies to all modules within that application.

Values specified in the manifest file of a web or EJB module are merged with the module scoped set of filters. This merged set of filters only applies to that module.

Exercise caution if you update a manifest file. Manifest files have line length limitations, and other constraints that must be adhered to.

Example:


com.ibm.ws.amm.scan.context.filter.disable.unifyTrue

Use this property only if we need to filter certain JAR files from annotation scanning by the Annotations Metadata Manager (AMM), but we want the files to be scanned by the Extensible Class Scanner (ECS) layer. To enable this property, set the value to true.

The default is false.


com.ibm.ws.amm.scan.context.filter.packages.

Provide a list of Java Packages that do not contain annotations. The Java classes specified for this property are not scanned for annotations.

When a Java EE 5 or 6 application is deployed or updated, the Annotations Metadata Manager (AMM) facility scans all of the annotation metadata. This scanning process can negatively affect the amount of time required to deploy an application. If the application includes Java Packages that do not contain annotations, we can list them as the value for this property. If the application includes archives or utilities that do not contain annotations, we can list them as the value for the Ignore-Scanning-Archives property.

The values specified for this property are case-sensitive and must be expressed as a single string with a comma followed by a space used to separate the names of the Java Packages. Wildcards and REGEX expressions are not permitted.

As an alternative to using this custom property, we can add the Ignore-Scanning-Packages property to one of the following files or modules, and specify the archives and utilities that we do not want scanned as the value of that property:

Values specified in the amm.filter.properties files are merged with those found in this custom property to form a server scoped set of filters. This merged set of filters applies to all of the applications deployed on that server.

Values specified in the manifest file of an application are merged with the server scoped set of filters to form a module scoped superset that applies to all modules within that application.

Values specified in the manifest file of a web or EJB module are merged with the module scoped set of filters. This merged set of filters only applies to that module.

The following example is properties file centric and cannot be used as is for a manifest file. Manifest files have a 72-byte line length limit, as well as other constraints that must be adhered to.

Example:


com.ibm.ws.application.enhancedScanning

Disable several optimizations that decreases the time to deploy and start enterprise applications. The optimizations primarily involve Java Platform, Enterprise Edition (Java EE 5)-enabled applications. When false, the following updates are disabled:

If set to false, we might experience decreases in performance. Default is true.


com.ibm.ws.cache.CacheConfig.alwaysSetSurrogateControlHdr

Force the surrogate-control header from the dynamic cache service to always be set on the response. The surrogate-control header contains the metadata that the Edge Side Include (ESI) processing needs to correctly generate, and invalidate the cached content in the ESI cache.

The default is false, which means that the surrogate-control header might not be set on the response.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.cache.CacheConfig.cascadeCachespecProperties

Enable child pages or fragments to inherit the cascade of save-attributes, and store-cookies properties from their parent pages or fragments. The default is false.

The default behavior of the dynamic cache service is to store the request attributes for a child page or fragment, if not explicitly overridden in the cache specification. An application server can run into an Out-Of-Memory condition in scenarios where these request attributes get too large. If the attributes saved by default are not serializable, then the disk offload of these cache entries results in java.io.NotSerializableExceptions.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.cache.CacheConfig.filteredStatusCodes

Indicate error situations in which we do not want the dynamic cache service to cache the servlet output.

The value specified for this property is a space delimited list of HTTP response error codes. If the status code that is returned from a cache miss matches one of the listed response error codes, the dynamic cache service does not cache the data that was obtained in response to an HTTP request.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.cache.CacheConfig.use61EntrySetBehavior

Return a set view of the mappings contained in the map.

When com.ibm.ws.cache.CacheConfig.use61EntrySetBehavior is defined and set to true the DistributedMap.entrySet() method returns a set view of the mappings contained in the map.

This custom property can be set as a JVM custom property at Servers > Application servers > <server name> > Process definitions > Java Virtual Machine > Custom properties.

Define this JVM custom property affects all cache instances. Specified at the application server level.


com.ibm.ws.cache.CacheConfig.useServerClassLoader

Specify which classloader the JVM should use when deserializing an InvalidationEvent. If we set this property to true, the server classloader is used to deserialize the InvalidationEvent. If set to false, the application classloader is used to deserialize the InvalidationEvent. The default is false.

Use the appropriate classloader when deserializing an InvalidationEvent helps improve performance.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.CacheConfig.alwaysTriggerCommandInvalidations

Ensure that command invalidations are triggered regardless of the skipCache attribute.

When a request object contains the <previewRequest> attribute the dynamic cache sets the skipCache attribute to true. When the skipCache attribute is true, commands are not always invalidated. Set to true to ensure that command invalidations are triggered regardless of the skipCache attribute. When we set this custom property, it affects all cache instances. The default is false.

This custom property is set on the application server level only.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.cdi.immediate.ejb.start

Ensure that the contexts and dependency injection (CDI) container and its lifecycles start for all EJB modules when the application starts.

When set to a value of true, the CDI container and its lifecycles start for all EJB modules when the application starts. The default value for this property is false.


com.ibm.ws.classloader.allowDisposedClassLoad

Specify whether the JVM should fully dispose of an application class loader when the application is stopped. If the JVM does not fully dispose of an application class loader, classes can still be loaded from that class loader.

When set to a value of true, the JVM does not fully dispose of an application class loader when the application is stopped.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.classloader.encodeResourceURLs

Specify whether the application class loaders, such as EAR, web module, and shared library loaders encode spaces in resource URLs. If set to true, spaces are encoded as "%20" in the URLs that either a getResource or getResources call returns.

Default is true. If set to false, warning message WSVR0333W displays in the logs. This message indicates that the use of the false setting for this property is deprecated.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.classloader.strict

Enable the WAS application class loader to provide access to the META-INF directory through a getResources call even if the META-INF directory path does not include a trailing slash

The WAS application class loader does not, by default, provide access to the META-INF directory through a getResources call unless a trailing slash is specified at the end of the META-INF directory path. If we want the WAS application class loader to provide access to the META-INF directory through a getResources call even if a trailing slash is not specified at the end of the META-INF directory path, set this property to true.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.

Important: Ensure that we use the resources that don't begin with a forward slash (/). The WAS class loader behaves consistently with the Java Underclassman using this property, which prohibits getResource calls that begin with a forward slash (/).


com.ibm.ws.classloader.zipFileCacheSize

Specify the maximum number of application JAR files that can be held open for resource and class loading. Reducing the number of times JAR files must be opened, improves the performance of applications that are resource or class loading intensive.

When the specified limit of open JAR files is reached, the class loader starts to close and remove JAR files based on the last time they were accessed. The most recently accessed JAR files are kept open. The value specified for this property should be based on the total number of application JAR files that are frequently accessed.

The default value for this property is 8. Specifying a value of 0 disables the cache and prevents application JAR files from being held open.

Avoid Trouble: Do not use the Microsoft Windows Hot Deployment function if we specify a value other than 0 for this property..

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.cscope.HighlyAvailableIORsEnabled

Allow the administrator to configure the compensation service to generate highly available IORs for distributed business activity CORBA objects, which enable distributed subordinate business activities that have failed to be completed during peer recovery. This property also permits new business activities when the nodeagent is not running.

The default value for this property is false. Specifying a value of true enables this property. This property should be set on each application server in the cluster.

com.ibm.ws.eba.bla.MapRolesToUsersStep.SkipValidation

Disable validation of users and groups when mapping roles to users for OSGi (Open Services Gateway initiative) applications. Indicate whether the MapRolesToUsersStep option validates specified users or groups against the user registry.

The default is false. Specify true to disable the validation. When using this custom property, specify the custom property as an application server JVM custom property.


com.ibm.ws.ecs.force.context.classloader

Use this property to avoid or activate steps to ensure that shared libraries are available for servlet container initializer testing.

The default values are unset or false. Possible values are unset, false, or true. Set the value to unset or false to avoid the steps to ensure that shared libraries are available for servlet container initializer testing. Set the value to true to take the steps to ensure that servlet container initializer testing includes shared libraries in the class path used for the tests.


com.ibm.ws.el.reuseEvaluationContext

The same EvaluationContext object can be reused on a per thread basis.

Typically, during the evaluation of expressions the Unified EL code creates a new org.apache.el.lang.EvaluationContext object for each call that is made. Because these objects are subsequently made available for garbage collection, as the number of objects created increases, memory consumption and garbage collection also increases. Setting the com.ibm.ws.el.reuseEvaluationContext property to true enables the same EvaluationContext object to be reused on a per thread basis, thereby decreasing memory consumption and the amount of garbage collection that needs to occur.

The default is false.


com.ibm.ws.http.ConnectionIOTimeout

Extend the timeout of the SOAP port between the time a connection is established and the time transmission of data from the client begins. The default is 5 seconds (15 seconds on Liberty). This might need to be increased if a SOAP server or client JVM is busy, or an SSL handshake is taking an extended period of time. An HTTP 408 message might be received from the SOAP server if this timeout occurs.


(ZOS) com.ibm.ws.iiop.channel.disableOnewayLocateRequiredMessage

Control whether the CWZGB0005I message displays whenever a oneway GIOP request against an object requires further locate-forward addressing. If the property is set to false, the CWZGB0005I message is displayed. If the property is set to true, the CWZGB0005I message is not displayed.

The default is false.


com.ibm.ws.jsf.allow.interpolator.per.app

The JSF container has been updated to allow a MessageInterpolator to be defined and used for each application, and it is not shared across applications. This property must be set to true for the new behavior to be enabled:


com.ibm.ws.jsf.call.publishevent.with.sourceclass

Ensure that the proper source class is used when calling javax.faces.Application.publishEvent. By default, when calling javax.faces.Application.publishEvent, the UIComponent.class is always used rather than the actual source class. However, the sourceBaseType parameter should indicate the source event that must be used to lookup the listener to which this event must be published. If this argument is null the return from source.getClass() must be used as the sourceBaseType.  

The default is false.


com.ibm.ws.jsp.enhance_el_support

Control how an expression is handled. During the evaluation of an expression, the value is coerced to the expected type based on Section 1.8.2 of the Expression Language Specification v2.1. This coercion can result in unexpected results as the expression value might not be the expected type. Set to true to prevent this coercion.

The default is false.


com.ibm.ws.management.application.task.AppTypeDeploymentTask.isLongRunningApp

This property is listed for informational purposes only. This property is created automatically and is used for auto-configuration and should not be changed.

Default is true.


com.ibm.ws.management.connector.soap.logClientInfo

Indicate whether we want to log the host, port, and username of SOAP client requests. When true, SOAP client details are logged in SystemOut.log. These details are also added to trace.log if the trace level for the SOAP connector is set to all.

The default is false.

(Windows)

com.ibm.ws.management.connector.soap.waitBeforeCloseTime

Change the length of time specified for the server SOAP connection timeout. When using the localhost adapter on a Microsoft Windows operating system, the server SOAP connection timeout, which defaults to 10 milliseconds, allows large amounts of data to be streamed without interruption.

If too short a length of time is specified for this property, a SOAPException for premature end of stream might occur on the server side of the connection when a large amount of data is streamed.

Specify a value of 0 disables the timeout.


com.ibm.ws.management.event.max_polling_interval

Specify the maximum amount of time the server waits before it asks or gets notifications from the client. The default polling interval is 1000 milliseconds (1 second). If a property value is not specified, the default value is used.

If we are using a SOAP or IPC connector, we can use this property to tune that connector such that the amount of time the server waits for a poll notification from the client matches the time interval the server would wait if you were using an RMI connector.

If this property value is set to -1, the client polls for notifications based on a built-in adaptive algorithm that changes the polling interval based on the number of notifications that the client receives. A time interval of 3 to 20 seconds can elapse between polls before the first notification is received.

For transitioning users: Prior to v8.0, if a value was not specified for the com.ibm.ws.management.event.max_polling_interval property, client polls for notification were based on the built-in adaptive algorithm that changes the polling interval based on the number of notifications that the client receives.trns

This property must be specified for the client-side JVM.


com.ibm.ws.management.event.pull_notification_timeout

Amount of time the client waits before polling notification from the server. The default timeout is 60000 milliseconds (60 seconds or 1 minute). If a property value is not specified, the default value is used.

If the property value is set to 0 (zero) or to a negative number such as -1, the server returns to the client immediately even if no notification is available.

For transitioning users: Prior to version 8.0, if a value was not specified for the com.ibm.ws.management.event.pull_notification_timeout property, the server returned to the client immediately even if no notification was available.trns

This property must be specified for the server-side JVM.


com.ibm.ws.management.repository.tempFileKeepTimeMinutes

Specify, in minutes, how long a file is kept in the configuration repository temporary directory before the configuration repository temporary directory cleanup task can delete that file from the directory. The default value for this property is 1440 minutes, which is equal to 24 hours. In previous versions of the product, a file was kept for 60 minutes.

The default is typically sufficient for performing needed cleanup without deleting files in use. However, there might be situations where we need to specify a larger, or smaller value. We can specify a minimum value of 60 minutes for this property. However, IBM recommends specified a value that is equivalent to several hours to account for situations where very large files are being transferred or synchronized, or where a network is slow, and file transfer operations are taking a long time. In these situations, if too short a time period is specified, it is possible for a file to be deleted while it is still being transferred.

If the com.ibm.ws.management.repository.tempFileSweepIntervalMinutes property is set to 0, the cleanup function is disabled, and any files that remain behind after a server process failure, remain in the configuration repository temporary directory until they are manually removed, or the cleanup function is enabled.

If an invalid value is specified for this property, the default value is used.


com.ibm.ws.management.repository.tempFileSweepIntervalMinutes

Specify, in minutes, how frequently the configuration repository temporary directory cleanup task runs. This task removes files from the configuration repository temporary directory that were not properly removed because of a server process failure.

The cleanup task always runs when the server starts, and then again after the time length that is specified for this property expires. The default value for this property is 720 minutes, which is equivalent to 12 hours. This length of time is typically sufficient for the configuration repository temporary directory cleanup task to successfully complete the cleanup process. We can disable this cleanup function by setting this property to 0.

In previous versions of the product, the cleanup task ran when the server started, and then ran again every 30 minutes.

If an invalid value is specified for this property, the default value is used.


com.ibm.ws.management.suppressPortScan

Set to a value of true to suppress port activity checking by the deployment manager when new servers are created. When set to true, the deployment manager does not attempt to bind or connect to a new port before using the port in a server configuration. Suppression of port activity checking can lead to port conflicts if other applications have active ports. The default is false.


com.ibm.ws.management.taskcommandtimeoutsec

Set to a value in seconds if a SessionTimeoutException from TaskCommandSessionMgr occurs when performing a long running application update. The default is 1200 seconds (20 minutes).


com.ibm.ws.odr.plugincfg.config.ASDisableNagle

Specify whether we want to disable the Nagle algorithm for the connection between the plug-in and the proxy server.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false, which means that the Nagle algorithm is enabled for the connection between the plug-in and the proxy server.


com.ibm.ws.odr.plugincfg.config.AcceptAllContent

Specify whether we can include content in POST, PUT, GET, and HEAD requests when a Content-Length or Transfer-encoding header is contained in the request header. We can specify one of the following values for this attribute:

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.config.AppServerPortPreference

Specify which port number is used to build URIs for a sendRedirect.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is HostHeader.


com.ibm.ws.odr.plugincfg.config.ChunkedResponse

Specify whether the plug-in groups the response to the client when a Transfer-Encoding : Chunked response header is present in the response.

Specify one of the following for this attribute:

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.config.IISDisableNagle

Specify whether we want to disable the nagle algorithm.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.config.IISPluginPriority

Priority in which the web server loads the plug-in. We can specify one of the following values for this attribute:

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is High.


com.ibm.ws.odr.plugincfg.config.IgnoreDNSFailures

Specify whether the plug-in is to ignore DNS failures within a configuration when started.

When true, the plug-in ignores DNS failures within a configuration and starts successfully if at least one server in each ServerCluster resolves the host name. Any server for which the host name is not resolved is marked unavailable for the life of the configuration. The host name is not resolved later during the routing of requests. If a DNS failure occurs, a log message is written to the plug-in log file and the plug-in continues initializing instead of the web server not starting.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.config.RefreshInterval

Specify, in seconds, how frequently the plug-in should check the configuration file for updates or changes. The plug-in checks the file for any modifications that occur since the plug-in configuration was loaded.

In a development environment where frequent changes occur, set the time interval to less than 60 seconds.

In a production environment, we should set a higher value than the default value because updates to the configuration do not occur as frequently.

If the plug-in reload is not successful, the plug-in log file contains an error message, and the previous configuration is used until the plug-in configuration file successfully reloads. Refer to the plug-in log file for more information if an error occurs.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is 60.


com.ibm.ws.odr.plugincfg.config.ResponseChunkSize

Specify, in kilobytes, the maximum chunk size the plug-in should use when reading the response body. For example, Config ResponseChunkSize="N", where N equals the chunk size.

By default, the plug-in reads the response body in 64k chunks until all of the response data is read. This process might cause a performance problem for requests where the response body contains large amounts of data. If the content length of the response body is unknown, a buffer size of N kilobytes is allocated and the body is read in N kilobyte size chunks until the entire body is read. If the content length is known, then a buffer size of either content length or N is used to read the response body.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is 64.


com.ibm.ws.odr.plugincfg.config.VHostMatchingCompat

Specify whether the plug-in should use the port number for virtual host matching. The following values can be specified:

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.config.TrustedProxyEnable

Specify whether the plug-in is to allow the inclusion of trusted proxies. The following values can be specified:

The trusted proxies are collected from the defined trusted security proxies.

This property is only valid for a proxy server, and applies to the Config element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.log.Name

Specify the fully qualified path to the log file to which the plug-in writes error messages.

This property is only valid for a proxy server, and applies to the Log element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is profileRoot/logs/http_plugin.log.


com.ibm.ws.odr.plugincfg.log.LogLevel

Specify the level of detail of the log messages that the plug-in writes to the log. Specify one of the following for this attribute:

This property is only valid for a proxy server, and applies to the Log element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is Error.

A lot of messages are logged at the trace level, which can cause the file system to fill up very quickly. Never use a trace setting in a normally functioning environment as it adversely affects performance.


com.ibm.ws.odr.plugincfg.cluster.CloneSeparatorChange

Indicate to the plug-in that the plus character (+) can be used as the clone separator.

Some pervasive devices cannot handle the colon character (:) used to separate clone IDs with session affinity.

If we use this custom property, change the proxy server configurations such that the proxy server separates clone IDs with the plus character instead the colon character.

This property is only valid for a proxy server, and applies to the ServerCluster element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.cluster.LoadBalance

Specify the appropriate load balancing option: Round Robin or Random.

The round-robin implementation has a random starting point. The first proxy server is picked randomly. Round Robin is then used to pick proxy servers from that point forward. This implementation ensures that in multiple process-based web servers, all of the processes don't start by sending the first request to the same proxy server.

The Random implementation also has a random starting point. However, with this implementation all subsequent proxy servers are also randomly selected. Therefore, the same proxy server might get selected repeatedly while other proxy servers remain idle.

The default is Round Robin.


com.ibm.ws.odr.plugincfg.cluster.PostSizeLimit

Specify, in bytes, the maximum number of bytes of request content that the plug-in is allowed to attempt to send to a server. If a request is received that is greater than the specified value, the plug-in ends the request

This property is only valid for a proxy server, and applies to the ServerCluster element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is -1, which indicates that there is no limit to the size of a request.


com.ibm.ws.odr.plugincfg.cluster.RemoveSpecialHeaders

Use this property to whether the plug-in is to add special headers to a request before it is forwarded to the server. These headers store information about the request that the application then uses. By default, the plug-in removes these headers from incoming requests before adding the required headers.

If set to false, we introduce a potential security exposure header from incoming requests are not removed.

This property is only valid for a proxy server, and applies to the ServerCluster element in the plugin-cfg.xml file that the proxy server automatically generates.

Default is true.


com.ibm.ws.odr.plugincfg.cluster.RetryInterval

Specify, in seconds, the amount of time that elapses between when a proxy server is marked down and when the plug-in reattempts to make a connection.

This property is only valid for a proxy server, and applies to the ServerCluster element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is 60.


com.ibm.ws.odr.plugincfg.odrIncludeStopped

Specify whether the plug-in is to allow the inclusion of stopped proxy servers. The following values can be specified:

This property is only valid for a proxy server.

The default is false.


com.ibm.ws.odr.plugincfg.server.ConnectTimeout

Specify, in seconds, the amount of time the plug-in waits for a successful connection

Specify a value for the property enables the plug-in to perform non-blocking connections with the proxy server. Such connections are beneficial when the plug-in is unable to contact the destination to determine if the port is available or unavailable.

When a value greater than 0 is specified, and a connection does not occur after that time interval elapses, the plug-in marks the proxy server unavailable, and proceeds with one of the other proxy servers defined in the cluster.

If no value is specified for this property, the plug-in performs a blocking connect in which the plug-in waits until an operating system times out and allows the plug-in to mark the proxy server unavailable.

This property is only valid for a proxy server, and applies to the Server element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is 0.


com.ibm.ws.odr.plugincfg.server.ExtendedHandShake

Indicate to the plug-in that it must ensure the availability of a proxy server before sending a request to that proxy server.

Typically, the plug-in marks a proxy server as stopped when a connect() ends. However, when a proxy firewall is between the plug-in and the proxy server, the connect() succeeds, even though the back-end proxy server is stopped. This situation causes the plug-in to not failover correctly to other proxy servers.

This property is only valid for a proxy server, and applies to the Server element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.server.MaxConnections

Specify the maximum number of pending connections to a proxy server that can flow through a Web server process at any point in time.

This property is only valid for a proxy server, and applies to the Server element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is -1, which indicates that there is no maximum number for the number of pending connections to a proxy server that can flow through a Web server process at any point in time.


com.ibm.ws.odr.plugincfg.cluster.WaitForContinue

Specify whether to use the HTTP 1.1 100 Continue support before sending the request content to the proxy server.

Typically, the plug-in does not wait for the 100 Continue response from the proxy server before sending the request content. We should use HTTP 1.1 100 Continue support when configuring the plug-in to work with certain types of proxy firewalls.

This property is ignored for POST requests to prevent a failure from occurring if the proxy server closes a connection because of a time-out.

This property is only valid for a proxy server, and applies to the Server element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.property.ESIEnable

Enable or disable the Edge Side Include (ESI) processor. If the ESI processor is disabled, the other ESI elements in the file are ignored.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

Default is true.


com.ibm.ws.odr.plugincfg.property.ESIMaxCacheSize

Specify, in 1 KB units, the maximum size of the cache. The default maximum size of the cache is 1024 KB (1 megabyte). If the cache is full, the first entry to be evicted from the cache is the entry that is closest to its expiration time.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is 1024.


com.ibm.ws.odr.plugincfg.property.ESIInvalidationMonitor

Specify whether the ESI processor receives invalidations from the proxy server.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is false.


com.ibm.ws.odr.plugincfg.property.https.keyring

Specify the directory location of the SAF keyring when the protocol of the transport is set to HTTPS.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is profileRoot/etc/plugin-key.kdb.


com.ibm.ws.odr.plugincfg.property.https.stashfile

Specify the location of the stashfile.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is profileRoot/node/etc/plugin-key.sth .


com.ibm.ws.odr.plugincfg.property.PluginInstallRoot

Specify the installation path for the plug-in.

We must set this property, to the fully qualified path of the plug-in installation root. If we use the default value, the property does not display in the plugin-cfg.xml file.

This property is only valid for a proxy server, and applies to the Property element in the plugin-cfg.xml file that the proxy server automatically generates.

The default is "".


com.ibm.ws.pm.checkingDBconnection

Specify whether the persistence manager is to continue checking the availability of a database that was previously marked as unavailable until a connection with that database is successfully established.

If a database service is down when the persistent manager attempts to establish a connection to that database, the database is marked as unavailable. Typically, the persistent manager does not re-attempt to establish a connection after a database is marked as unavailable. If we sent this property to true, the persistence manager continues to check the availability of the database until it is able to successfully establish a connection to that database.

The default is false.


com.ibm.ws.policyset.exportEncodedPasswords

Set the property to true to enable WS-Security policyset bindings that include encrypted passwords to be exported using XOR encoded passwords instead.

Valid values are true and false.

The default is false.


com.ibm.ws.readSystemLocale

Set to true if the code needs to process JAX-WS SOAP messages using an encoding other than the one specified in the message, or, if no encoding is specified, the code needs to process the messages using Unicode Transformation Format, 8-bit encoding form (UTF-8). If set to true, the encoding used is the one specified by the file.encoding JVM property. The default is false.


com.ibm.ws.recoverylog.disableNonHARegistration

When the application server is not a member of a cluster that has failover of transaction log recovery enabled, it is not necessary for the recovery log service to register with the HA Manager.

However, if failover is later enabled, and only a partial restart of the cluster occurs, set this custom property to true so that the recovery log service does not register with the HA Manager.

Valid values are true and false.

The default is false.


com.ibm.ws.recoverylog.spi.NoMemoryMappedFiles

Provide a performance improvement for the memory mapping of the transaction log files if the logs are local to the application server.

However, if the transaction logs are defined on a remote file system, which is typical when we enable High Availability (HA) support, any performance gains are negligible. Additionally, the log processing is more complex. Because of this complexity, in an HA environment memory, disable the mapping of the transaction logs.

To disable the memory mapped files, set the JVM custom property of com.ibm.ws.recoverylog.spi.NoMemoryMappedFiles to true on any server that accesses recovery log files. The default is false.

Remember: By default, memory mapping of the transaction logs is disabled on the z/OS operating system, and on the Windows operating system within an HA environment.


com.ibm.ws.runtime.component.ResourceMgr.postBindNotify

Make the Connection Factory MBeans available when a resource adapter starts. Typically, when a resource adapter starts, the Connection Factory MBeans are not available for the resource adapter to query. However, certain resource adapters, such as the IMS™ DB Resource Adapter, require this function for initialization.

If we are not using a resource adapter that requires the availability of Connection Factory Beans at initialization, add this property to the JVM settings and set the value to false.

Default is true.


com.ibm.ws.runtime.dumpShutdown

There are differing situations where a thread dump during server shutdown is useful. The following are examples

The com.ibm.ws.runtime.dumpShutdown diagnostic custom property allows us to trigger a Java core thread dump during server shutdown. Set to true to trigger a Java core thread dump during server shutdown. The default is false.

(AIX) (Windows) (Linux) (ZOS) For platforms where an IBM SDK is used (AIX, Windows, Linux, z/OS), the Java core thread dump is generated in the working directory of the application server.

(Solaris) (HPUX) For other platforms (Solaris, HP-UX), the Java core thread dump is written into the native_stdout.log file for the application server.

In addition to the Java core thread dump, the stack trace of the current thread that is processing the shutdown is printed in the SystemErr.log for the application server.

com.ibm.ws.runtime.logThreadPoolGrowth

Thread pools allowed to grow are configured with a maximum size but allowed to increase in size beyond that maximum. However, by default, no messages are issued that indicate that the maximum size has been exceeded.

Set to true to have server to send a message to the log file when a thread pool that is allowed to grow increases beyond its configured maximum size.


com.ibm.ws.scripting.apptimeout

Specify, in seconds, the length of time that can elapse before an application installation, or an application update times out. The default is 86400, which is equivalent to 24 hours.

Specify a reasonable value for this property prevents the installation, or update process from continuing indefinitely when a situation occurs that prevents the installation, or update script from completing. For example, we might have a JACL script that updates an EAR file that cannot complete because the deployment manager that the script is connected to stops.


com.ibm.ws.sib.webservices.useSOAPJMSTextMessages

By default on WAS v6 or later, a SOAP over JMS web service message sent by the Web Services Gateway is sent as a JmsBytesMessage.

Set to true to modify the default behavior and send a compatible JmsTextMessage. Setting this property modifies the default behavior for all outbound JMS web services invocations sent from the service integration bus.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.soap.handleRST

Use this property if we want the web server to recognize when a SOAP message is read, and treat the RequestSecurityToken (RST) element as a FIN message type.

In some instances, when a connection reset occurs, a web server starts with security disabled. However, because a RST was received instead of the normal FIN/end of file, an error message appears in the administrative console indicating the web server failed to start, even though the web server did start and is operational. A refresh of the web server console page displays the correct operational status.

If we set the com.ibm.ws.soap.handleRST custom property to true, the web server will recognize when the complete SOAP message has been read, and treat the RST as a FIN, and we will not receive an error message when an RST is received.


com.ibm.ws.use602RequiredAttrCompatibility

Use the com.ibm.ws.use602RequiredAttrCompatibility custom property to specify whether the <required> attribute is evaluated prior to other attributes in the cachespec.xml file.

In v6.0.2, if we set the <required> attribute to false, then all of the other attributes within the cachespec.xml file are ignored and a cache ID is generated.

For transitioning users: In versions later than 6.0.2, by default, the <required> attribute is evaluated along with all of the other attributes to determine if a cache ID is generated.trns

If we set the com.ibm.ws.use602RequiredAttrCompatibility custom property to true, then the behavior of the cachespec.xml file is reverted back to the behavior in Version 6.0.2. The <required> attribute is evaluated prior to other attributes in the cachespec.xml file. The default is false.. When we set this JVM custom property, which only applies to the application server level, it affects all of the dynamic cache users.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


com.ibm.ws.webcontainer.allowDefaultErrorPage

Use this property if your web.xml file contains an error page definition that adheres to the Servlet 3.0 Specification. The Servlet 3.0 specification indicates that only the <location> parameter is mandatory. The <error-code> and <exception-type> parameters are optional. However, if we do not add this property to the JVM settings and set it to true, an error page defined with just the <location> parameter is ignored.

The default is false.

If we use this property, it must be set at the application server level.


com.ibm.ws.webservices.allowNoSOAPActionHeader

Enable the web services engine to tolerate an incoming web service request that does not contain a SOAPAction header. This property must be set at the application server level.

The SOAP specification states an HTTP request message must contain a SOAPAction HTTP header field with a quoted empty string value, if in the corresponding WSDL description, the soapAction of soapbind:operation is either not present, or present with an empty string as its value. However, if we want the web services engine to handle requests that do not contain a SOAPACTION header, add this property to the application server settings and set it to true.

When this property is not specified, or is not set to true, if an incoming SOAP request message does not contain a SOAPAction header, a SOAP Fault is returned to the client

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.allowStatusCode202OneWay

Allow a JAX-RPC one-way service to send a 202 status code instead of a 200 status code.

A JAX-RPC one-way service deployed on WAS normally returns a 200 HTTP status code. Some JAX-RPC implementations cannot tolerate a 200 status code, preferring a 202 instead. According to the Basic Profile Version 1.1, both 200 and 202 are valid status codes for one-way services.

If the property is set to true, then the JAX-RPC one-way service returns a 202 status code.

The default is false.

This property only applies to the application server JVM.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.appendRootCauseToWSF

If we are a JAX-RPC user, use this property to specify whether we want the Fault details for an exception that are returned in a response to contain information about the original exception.

Typically, the Fault details for an exception, that are returned in a response, only contains information about the most recent exception. It does not contain information about the original exception, which usually is not the most current exception. Frequently, an exception triggers other exceptions before the Fault details are returned in a response. This discrepancy can make problem determination more difficult for the end user if that person does not have access to the logs from the service provider.

If the end user needs to be able to see the exception details for all of the exceptions associated with a problem, this custom property should be set to true for the JVM on the service provider's application server. When this custom property is set to true on the service provider's application server, the application server loops though all the exception causes, and concatenates the details of each exception into the Fault details that are returned in the response.

The default is false.

If we decide to use this custom property, specify it as a JVM custom property for an application server.


(ZOS) com.ibm.ws.webservices.cacheEngineList

In WAS for z/OS configurations using JAX-RPC web services, use this property to disable client web services engine caching.

If an application is restarted several times, the client engine cache might fill local system storage, causing an out-of-memory error. When true, engine caching is enabled. Set to false to disable engine caching when this out-of-memory error occurs.

Default is true.


com.ibm.ws.webservices.contentTransferEncoding

Specify a range of bits for which .XML-encoding is disabled. Typically any integer that is greater than 127 is XML-encoded. When we specify this property:

Specify 7bit, if we only want integers greater than 127 encoded. Specify 8bit, if we only want integers greater than 255 encoded. Specify binary, if we want encoding disabled for all integers.

The default is 7bit.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.disableSOAPElementLazyParse

Disable lazy parsing of SOAPElements. Lazy parsing is designed for situations where the client is not parsing the SOAPElement. If a client is parsing the SOAPElement with SAAJ, it is better to not delay parsing by the web services component.

We can set this property as a JVM custom property at either the server or client level. When this property is set at either the server or client level, the setting applies to all applications on the JVM. The default is false.

We can also use an application assembly tool to specify this property as a new web service description binding entry for the port component binding, to disable lazy parsing of SOAPElements on an application-by-application basis for a particular server, instead of for all of the servers managed by the deployment manager.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.engine.transport.jms.propagateOneWaySystemExceptions

Enable exceptions that occur during the processing of a one-way JMS Web service to be propagated back to the EJB container. This propagation makes normal error recovery possible.

If set to false, an exception is wrapped in a WebServicesFault message and sent back to the client. Because the web service is not aware of the exception, no recovery is attempted.

The default is false.

This property does not apply to a one-way HTTP Web service, or to two-way JMS requests.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.forceLegacyDispatchFromSOAPConnection

Specify that the JAX-RPC engine is to be used to process outgoing requests for SOAP with Attachments API for Java (SAAJ) clients, instead of the JAX-WS engine.

This property does not apply to web services clients that use the JAX-RPC or JAX-WS APIs to invoke web services. When the JAX-WS engine is used to process client requests, the outcome might be different than when the JAX-RPC engine is used. For example, some SAAJ clients set the SOAPAction header as a MIME header, using the SAAJ APIs. When the JAX-RPC engine is used to process such a request, this SOAPAction header with its user-set value is sent in the request. However, if the JAX-WS engine is used to process the same request, an empty SOAPAction header is sent in the request. If we are used to having the JAX-RPC engine process SAAJ client requests and want to preserve this behavior, add this property to the JVM settings and set it to true.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.HttpRedirectWithProxy

Set to true to allow HTTP redirect requests to be sent through the proxy server. When true, we change the default behavior for all outbound HTTP redirect requests sent from the JAX-RPC runtime. When false, a redirect request is sent to a remote server directly even though a proxy server is configured.

The default is false.

If we decide to use this custom property, specify it as a proxy server JVM custom property.


com.ibm.ws.webservices.ignoreUnknownElements

Control whether clients can ignore extra XML elements that are sometimes found within literal SOAP operation responses.

Set to true provides you with the flexibility of being able to update the server code to include more response information, without having to immediately update our client code to process this additional information. However, when this function is enabled, the checking of SOAP message against the expected message structure is more relaxed than when this property is set to false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.jaxrpc.parse.tolerate.invalid.namespace

Enable the JAX-RPC engine to use a more tolerant algorithm when determining whether to accept an incoming JAX-RPC message.

Typically, if an incoming JAX-RPC message uses an invalid namespace for a body element, the JAX-RPC engine rejects the message. If we set this property to true, the JAX-RPC engine uses a more tolerant algorithm that ignores the namespace mismatch.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.resolveXMLSchemaDTD

Enable a JAX-RPC application to properly start even if the schema or WSDL file represented in the _AbsoluteImportResolver class also references the http://www.w3.org/2001/XMLSchema.dtd DTD.

When we run on a host that is not connected to the Internet, a JAX-RPC application that is packaged with the _AbsoluteImportResolver class might not start properly. The following error might exist in the log files:

Set this custom property to true enables a JAX-RPC application to properly start even if the schema or WSDL file represented in the _AbsoluteImportResolver class also references the http://www.w3.org/2001/XMLSchema.dtd DTD.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.searchForAppServer

Control whether DualMetaDataLoaderImpl E loadWebContainerPorts could not find any http or https ports messages are sent to the system log.

Depending on the system configuration, if a web services application is installed across both a web server and an application server, the system might issue this message, indicating an error occurred even though this is a valid configuration. Therefore, if we install any of our web services applications across both a web server and an application server, we might not want these messages sent to the system log.

If the com.ibm.ws.webservices.searchForAppServer property is set to true, any DualMetaDataLoaderImpl E loadWebContainerPorts could not find any http or https ports messages that are issued are not sent to the system log. If this property is not specified or is set to false, these messages are sent to the system log.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.serialize.2DimArray.asArrays

Cause the JAX-RPC runtime to serialize two-dimensional XML arrays as a series of arrays.

If we decide to use this custom property, specify it as an application server JVM custom property.

The default is false.

The following message snippet illustrates a series of elements, which is a valid format for representing two-dimensional XML arrays when this property is set to false.


com.ibm.ws.webservices.serializeDetailElementUsingDefaultNamespace

Specify whether the application server uses an actual prefix name to locate the namespace that defines the Fault detail, or uses a default namespace to define the Fault detail.

When a JAX-RPC Web service responds with a SOAP Fault, an actual prefix name is typically used to locate the namespace that defines the contents of the Fault detail. Following is an example of the message that the application server typically issues in this situation:

If the application server needs to communicate with .Net clients, and these .Net clients require the use of a default namespace to define the contents of the Fault detail, set this property to true. When true, the message that the application server issues is similar to the message that was sent from a version previous to a v6.x application server.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.webservices.suppressHTTPRequestPortSuffix

Control whether a port number can remain in an HTTP POST request that sends a SOAP message.

Some web service implementations do not properly tolerate the presence of a port number within the HTTP POST request that sends the SOAP message. If we have a web service client that needs to interoperate with web service that cannot tolerate a port number within an HTTP POST request that sends a SOAP message, set this custom property to true.

When true, the port number is removed from the HTTP POST request before it is sent.

We must restart the server before this configuration setting takes effect.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.AppendAcceptHeader

Specify a string to append to the HTTP Accept header sent by JAX-WS web service requests. The default is null.


com.ibm.ws.websvcs.attachments.sizethreshold

Specify, in bytes, the maximum size of an attachment on the JAX-WS client or service that can be written to memory. By default, the maximum attachment size is set to 11 MB. With this value, if an attachment exceeds 11 MB, it is cached to the file system instead of written to memory. When we use this custom property, as we increase the maximum cache size, there is a greater impact on performance and potentially to the Java heap.

To specify the maximum size of an attachment on the JAX-RPC client or service, see the com.ibm.websphere.webservices.attachements.maxMemCacheSize custom property.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.dynamic.ssl.proxy

Turn off web services annotation scanning at the server level. By default, web services annotation scanning is enabled at the server level.

To turn off annotation scanning at the application level, set the DisableIBMJAXWSEngine property in the META-INF/MANIFEST.MF of a WAR file or EJB module to true.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.getJAXBContext.cacheClassList

Cache a list of the Java Architecture for XML Binding (JAXB) classes contained in a package.

Typically, when building a JAXBContext, if a package does not contain either a ObjectFactory or package-info class file, the package is searched for all potential JAXB classes. This search process can be time consuming and can be delayed by JAR file locking. Set to true to cache the class list for each package, eliminating the need for subsequent searches of the same package. Later JAXBContext creation requests retrieve the cached version of the class list instead of initiating a new search.

Because the class list cache is created using a SoftReference, the cache can be released if available memory becomes low.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.getJAXBContext.cacheClassList.persist

Create a disk cache of the Java Architecture for XML Binding (JAXB) classes contained in a package.

Typically, when building a JAXBContext, if a package does not contain either a ObjectFactory or package-info class file, the package is searched for all potential JAXB classes. This search process can be time consuming and can be delayed by JAR file locking. Set to true to create a disk cache of the class list for each package, eliminating the need for subsequent searches of the same package. Later JAXBContext creation requests retrieve the cached version of the class list instead of initiating a new search.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.logOperationExceptionAsDebug

SOAP fault exceptions are always written using log.error, which is written to SystemOut.log as well the Trace.log. Ensure that SOAP fault exceptions are logged to ONLY Trace.log when tracing is enabled, and NOT to SystemOut.log. The property does not distinguish the type of SOAP fault exceptions logged in SystemOut.log.

SOAP fault exceptions are only seen in Trace.log when web services traces are turned on and when com.ibm.ws.websvcs.logOperationExceptionAsDebug=true.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.saaj.converter.defaultReturnEncoding

Convert data for a JAX-WS handler to use a different encoding from the JVM default. For example, -Dcom.ibm.ws.websvcs.saaj.converter.defaultReturnEncoding=UTF-8. The default is unset.


com.ibm.ws.websvcs.suppressHTTPRequestPortSuffix

Prevent the JAX-WS runtime from appending the port number to the HTTP Host header value to a request.

A JAX-WS client might receive a java.io.IOException in response to a request, especially if there is a non-IBM web server located between the client and the web service the client is trying to call. This intermediary server might not understand where to route the request because the JAX-WS runtime has appended the port number to the HTTP Host header value. For example, JAX-WS runtime might have changed the header value from the endpoint URL lilygirl.austin.mycompany.com to the URL lilygirl.austin.mycompany.com:80, which includes the port number.

To prevent the JAX-WS runtime from appending the port number to the HTTP Host header value, add this custom property to the JVM settings, and set it to true. When true, the Host header only contains the hostname of the endpoint URL, for example, Host: lilygirl.austin.mycompany.com

The default value for this property is false, which means that, the port number is appended to a Host header value.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.transport.enableProxyTunnel

Set to true to enable the web services client to access resources through a web proxy server. Default is false. which indicates that tunneling is not to be used in the web services transport layer for proxies.

Example: By leaving the default setting of false, a JAX-WS web service client that attempts to call a remote web service over HTTPS experiences an exception when the call is directed through an HTTP server configured as a forward proxy.

The default is false.

If we decide to use this custom property, specify it as a proxy server JVM custom property.


com.ibm.ws.websvcs.relaxClientPolsetMatching

Use this property to allow JAX-WS client-side policy sets to be applied at the service or lower level through the administrative console when the client code spans more than one archive file.

The default is false.


com.ibm.ws.websvcs.transport.jms.enableBasicAuthOnResponse

Specify whether the JMS policy set basic authorization user ID and password is applied to JMS response messages. By default, the JMS policy set basic authorization user ID and password are not applied to JMS response messages.

If we add this property to the JVM settings, and specify true as the value of this property, the JMS policy set basic authorization user ID and password is applied to JMS response messages. If set to false, neither the user ID nor the password is applied.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.websvcs.unifyServiceMessage

Set to true to have JAX-WS applications display the JAX-RPC message, Hi there, this is a Web service!, in a browser window instead of the JAX-WS specific message Hello! This is an Axis2 Web Service! when a service URL is entered in a browser.

The default is false.


com.ibm.ws.websvcs.unmanaged.client.dontUseOverriddenEndpointUri

We might want a request by an unmanaged JAX-WS client service to be sent to the endpoint URL specified in the Overridden endpoint URL field on the administrative console. The value of this managed field, which is set as part of the web services client port configuration, overwrites the endpoint specified in the WSDL file. For more information on this field, read about the web services client port.

If we have either all managed clients or a mixture of both managed and unmanaged clients, we can edit the Overridden endpoint URL field in the administrative console. However, if we do not have any managed clients, we cannot edit the field.

Normally, we do not want an unmanaged JAX-WS client service to access this managed client service function. However, we might depend on unmanaged JAX-WS client services accessing this URL. By default, the com.ibm.ws.websvcs.unmanaged.client.dontUseOverriddenEndpointUri custom property is set to false to allow unmanaged JAX-WS client services to access the endpoint URL that overwrites the endpoint in the WSDL file.

This custom property is set on the application server level where a JAX-WS client is installed or a Java EE client exists if we run the launchClient.

If we decide to use this custom property, specify it as an application server JVM custom property.


com.ibm.ws.ws.wsba.protocolmessages.twoway

Improve the performance of an application server that is handling requests for Web Services Business Activities (WS-BA). Specifying true for this custom property improves application server performance when WS-BA protocol messages are sent between two application servers. Default is true.

If we decide to use this custom property, the property must be set on the application server that initiates the requests. It does not have to be set on the application server that receives the requests.

If we decide to use this custom property, we must specify it as an application server JVM custom property.


(ZOS) com.ibm.ws390.SystemOutErrCodepage

Specify an encoding schema for messages issued using System.out and System.err with the println, print, and write methods other than EBCDIC. If no encoding schema is specified, EBCDIC, which is the default encoding schema, is used for these messages.

The value specified for this property must be in string format.

If we decide to use this custom property, specify it as a JVM custom property for the servant.


com.ibm.wsspi.amm.merge.ignoreValidationExceptions

Use this custom property to indicate to the JVM that it should ignore validation exceptions that might occur during EJB processing. When an application is configured with necessary classes defined in shared libraries during EJB processing, incomplete information may be generated. As a result, a validation exception might occur and the following exception message may appear:

Set to true if we want the JVM to ignore these validation exceptions.

The default is false.

If we decide to use this custom property, specify it as a JVM custom property for the application server.


com.ibm.wsspi.wssecurity.dsig.enableEnvelopedSignatureProperty

Use this custom property to indicate to the JVM that we want the WS-Security runtime to verify an XML Digital Signature in the same manner as it did in Versions 7.0.0.21 and earlier, and 8.0.0.3 and earlier.

This property should only be set to true if the environment includes a cell that has application servers at different fix pack levels, and we are encountering compatibility problems.

In Versions 7.0.0.21 and earlier, and 8.0.0.3 and earlier, when WS-Security verifies an XML Digital Signature that uses the http://www.w3.org/2000/09/xmldsig#enveloped-signature transform algorithm, and the signed element has attributes with a namespace prefix, a Digest value mismatch error message, similar to the following error message, might occur:

If an element to be signed contains an attribute with a namespace prefix, the WS-Security runtime canonicalizes the element before calculating the digest value.

In this version of the product and in Versions 7.0.0.23 and higher and 8.0.0.4 and higher, the WS-Security runtime properly handles element attributes with namespace prefixes.

If we decide to use this custom property, specify it as a JVM custom property for the application server.


com.ibm.xml.xlxp.jaxb.opti.level

Use the com.ibm.xml.xlxp.jaxb.opti.level custom property to control whether optimization methods are enabled for Java Architecture for XML Binding (JAXB) unmarshalling (deserialization) and marshalling (serialization). The following table lists the supported values for this custom property and their effect on applications and web services.

Custom property value Effect
com.ibm.xml.xlxp.jaxb.opti.level=0 Optimization methods are not enabled.
com.ibm.xml.xlxp.jaxb.opti.level=1 Only unmarshalling optimization methods are enabled.
com.ibm.xml.xlxp.jaxb.opti.level=2 Only marshalling optimization methods are enabled.
com.ibm.xml.xlxp.jaxb.opti.level=3 Both unmarshalling and marshalling optimization methods are enabled, which is the default value.

For optimum performance, set the custom property value to 3. This value increases throughput for web services and applications that use JAXB directly. If we are experiencing issues with optimization after setting this value, change the value to 0 as a temporary workaround.

We can set this custom property on the application server level only.


com.ibm.xml.xlxp2.api.util.encoding.DataSourceFactory.bufferLength

Setting this JVM custom property to a smaller value such as 2048 can reduce the memory usage if the 64 KB buffers (the default) are only partially filled by the InputStream when they are in use. The buffers are cached within the XML parser com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader. A reduction in memory usage reduces the overall memory linked to each parser object.


com.ibm.xml.xlxp2.api.util.Pool.STRONG_REFERENCE_POOL_MAXIMUM_SIZE

The value of this system property is an integer, and when set, it limits the number of XMLStreamReaders and XMLStreamWriters that are cached using strong references.

To avoid an OutOfMemoryError, set the system property to 0. This forces all XMLStreamReaders to be cached using SoftReferences, and enables the garbage collector to reclaim the memory they occupy in the cache at any time.

When this system property is not set, the default value is 10.


config_consistency_check

Use this property to optionally turn off the default workspace consistency process. The deployment manager maintains a master configuration repository for the entire cell. By default, when the configuration changes, the product compares the configuration in the workspace with the master repository to maintain workspace consistency. However, the consistency verification process can cause an increase in the amount of time to save a configuration change or to deploy a large number of applications. The following factors influence how much time is required:

If the amount of time required to change a configuration change is unsatisfactory, we can add the config_consistency_check custom property to the JVM settings and set the value of this property to false.

The config_consistency_check custom property affects the dmgr process only. It does not affect other processes including the node agent and application server processes. The consistency check is not performed on these processes. However, within the SystemOut.log files for these processes, we might see a note that the consistency check is disabled. For these non-dmgr processes, we can ignore this message.


deactivateWildCardURIMapping

Enable the plugin-cfg.xml file generator to recognize the URI patterns specified on the file.serving.patterns.allow attribute in the ibm-web-ext.xmi file for a web application.

The plugin-cfg.xml file generator only recognizes the URI patterns specified on the file.serving.patterns.allow attribute if the FileServingEnabled attribute in that ibm-web-ext.xmi file is set to true. However, when the FileServingEnabled attribute is set to true, the plugin-cfg.xml file generator automatically adds the wildcard URI mapping, /*, to plugin-cfg.xml, which negates the usefulness of defining unique file serving patterns.

Set the deactivateWildCardURIMapping property to true prevents the plugin-cfg.xml file generator from adding the /* to plugin-cfg.xml, and enables plugin-cfg.xml generator to recognizes the URI patterns specified on the file.serving.patterns.allow attribute. If this property is not added to the JVM settings, or is set to false, the /* is automatically added to the plugin-cfg.xml file.

Set at the deployment manager level.


DISABLE_LOCAL_COMM_WHEN_SSL_REQUIRED

Specifies whether localComm or SSL should be used when transport level SSL is supported on the client or server side, and is required on the other side.

localComm should not be used when transport level SSL is supported on the client or server side, and is required on the other side. In this situation, we should set this custom property to true to ensure that SSL is used instead of localComm.

The default value for this property is false, which means that localComm is used.

If we decide to use this custom property, specify it as an application server JVM custom property.

When we specify this property for an application server:


disableWSAddressCaching

Disable address caching for web services. If the system typically runs with lots of client threads, and we encounter lock contention on the wsAddrCache cache, we can set this custom property to true, to prevent caching of the web services data.

If we specify networkaddress.cache.ttl with a value of zero or any other positive integer, this property must be set to true to avoid caching of an IP address in the webservice engine. Networkaddress.cache.ttl is used to indicate the number of seconds to cache a successful lookup.

The default is false.


DRS_BATCH_INTERVAL_SIZE

Maximum number of objects that can be included in a batch of Data Replication Service (DRS) replicated HTTP session data. If there are less than the specified number of objects in the HTTP session data being replicated, all of the session data is replicated in a single batch.

By default, DRS replicates 50 HTTP session data objects in a batch. Because serializing a large message can cause an out-of-memory condition, we might want to include a smaller number of objects in each batch, especially if we have application servers that join established, fully-populated, replication domains.

If we decide to use this custom property, specify it as an application server JVM custom property.


DRS_THREADPOOL_MINSIZE

Minimum number of threads to allow in the data replication service (DRS) thread pool.

When an application server starts, threads are not initially assigned to the thread pool. Threads are added to the thread pool as the workload that is assigned to the application server requires them and until the number of threads in the pool equals the number of threads specified by this custom property. After this point in time, additional threads are added and removed as the workload changes. However, the number of threads in the pool never decreases below the number that is specified by this custom property, even if some of the threads are idle.

The default value for this custom property is 40 threads.

If we decide to use this custom property, specify it as an application server JVM custom property.


DRS_THREADPOOL_MAXSIZE

Maximum number of threads to maintain in the DRS thread pool.

The default value for this custom property is 100 threads.

If we decide to use this custom property, specify it as an application server JVM custom property.


DRS_THREADPOOL_ISGROWABLE

Specifies whether the number of threads can increase beyond the maximum size configured for the DRS thread pool.

The maximum number of threads that can be created is constrained only within the limits of the Java virtual machine and the operating system. When a thread pool, that is allowed to grow, expands beyond the maximum size, the additional threads are not reused and are discarded from the pool after processing the work items for which they were created is completed.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


dynacache.jms.cacheInstance

When dynamic cache service multi-cell and multi-core group invalidation is enabled, use this property to specify the cache instance to use for processing invalidations. Setting this property to "*" causes invalidation IDs to be processed on all cache instances. This property should be set on the service integration bus servers.

By default, the baseCache cache instance is used. Use the administrative console to determine the names of the cache instances defined for our system.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


dynacache.jms.connRetryInterval

When dynamic cache service multi-cell and multi-core group invalidation is enabled, use this property to specify the number of seconds that a cluster member waits before attempting to reconnect to a service integration bus server.

The default value for this property is 30.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


dynacache.jms.invProcessingDelay

When dynamic cache service multi-cell and multi-core group invalidation is enabled, use this property to specify the number of seconds the service integration bus server queues invalidation IDs before processing them.

The default value for this property is 20.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


dynacache.jms.numStoredInvalidations

When dynamic cache service multi-cell and multi-core group invalidation is enabled, use this property to specify the maximum number of invalidation IDs a cluster member can store while waiting for a service integration bus server to become available. After the threshold is reached, the oldest invalidation IDs are removed as new IDs are added.

The default value for this property is 10000.

If we decide to use this custom property, specify it as an application server JVM custom property unless otherwise indicated within the context of a specific task.


(ZOS) invocationCacheSize

Control the size of the invocation cache. The invocation cache holds information for mapping request URLs to servlet resources. A cache of the requested size is created for each worker thread available to process a request. The default size of the invocation cache is 50. If more than 50 unique URLs are actively being used (each JavaServer Page is a unique URL), we should increase the size of the invocation cache.

A larger cache uses more of the Java heap, so we might also need to increase the maximum Java heap size. For example, if each cache entry requires 2 KB, maximum thread size is set to 25, and the URL invocation cache size is 100; then 5 MB of Java heap are required.

We can specify any number higher than 0 for the cache size. Setting the value to zero disables the invocation cache.

java.net.preferIPv4Stack

Disable IPv6 support. On operating systems where IPv6 support is available, the underlying native socket that the product uses is an IPv6 socket. On IPv6 network stacks that support IPv4-mapped addresses, we can use IPv6 sockets to connect to and accept connections from both IPv4 and IPv6 hosts.

Set to true disables the dual mode support in the JVM which might, in turn, disrupt normal product functions. Therefore, it is important to understand the full implications before using this property. In general, setting this property is not recommended.

The default value for this custom property is false.

java.net.preferIPv6Addresses

Disable IPv4 support. Setting this property to true disables the dual mode support in the JVM which might, in turn, disrupt normal product functions. Therefore, it is important to understand the full implications before using this property. In general, setting this property is not recommended.

The default value for this custom property is false.


java.util.logging.configureByLoggingPropertiesFile

Specify whether the JVM uses the logging.properties file to configure JSR-47 logging.

If this property is not added to the JVM configuration settings, or is set to false, the configuration settings contained in the logging.properties file are not picked up because the product overrides the base JSR47 logging configuration with the java.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager system property setting. In this situation, only logging settings that can be changed programmatically, such as the addition of handlers, and formatters, can be modified.

When true, the JVM still configures the WsLogManager as the LogManager, but during server startup, the logging configuration for applications using JSR-47 logging is initialized based on settings in the logging.properties file. Refer to the Java Utility Logging API documentation for valid logging properties and format that can be specified in the logging.properties configuration file.

Do not assign java.util.logging.ConsoleHandler to any of the loggers because this assignment can cause an infinite loop.

The logging.properties file is located in the <<WAS_install>>/java/jre/lib/logging.properties directory, and can be customized as needed.

(ZOS) The logging.properties file is located in the <<WAS_install>>/java/J*/lib/logging.properties directory, and can be customized as needed.

The default is false.


jaxws.asyncClient.maxThreadPoolSize

Use this property to limit the number of concurrently executing threads for JAX-WS async client requests.

By default the number of threads is not limited.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.handler.reducecaching

Ensure that JAX-WS handlers correctly update SOAP messages.

SOAP messages that are updated by a JAX-WS handler appear correct when dumped in the handler, but when a message is sent, the changes are missing. Set to true if your handler calls getMessage() multiple times and messages are lost.

This property is not compatible with modifying SOAP headers directly through JAX-WS message context properties. Using both types of message modification might cause information loss.

The default is false.


jaxws.ignore.extraWSDLOps

Use this property if there are more operations in the WSDL than built into the client.

Default client behavior is to validate the operations built into the client against the operations in WSDL and fail if they do not match. Set to true if there are more operations in the WSDL than built into the client and the WSDL validation will succeed and the client can be invoked.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.ignoreMetadataComplete

Set this JVM property to true to perform a webservice annotation scan even if metadata-complete is set on a module. The default is false.

In the default case, JAX-WS web services are not detected when metadata-complete is set to true.

This JVM property must be set on every JVM in the WAS cell.


jaxws.JAXBContext.permStoreCostThresholdMsec

Enable caching of JAXBContext objects that require more than the specified amount of time to construct.

JAX-WS web services or clients might experience delays during execution when constructing JAXBContext objects that handle hundreds of classes. Caching time-intensive JAXBContext objects accelerates web service and client execution by eliminating the need to reconstruct the JAXBContext object upon each use.

Set to a value, in milliseconds, that is greater than 0 to enable caching of JAXBContext objects that require more than the specified amount of time to construct. The cache persists until the JVM is restarted. The recommended value is 5000 milliseconds or greater.

The default is 0, which does not enable caching.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.JAXBContext.permStoreMaxSize

Set to an integer value to specify the maximum number of entries in the JAXBContext cache. If the cache becomes full, stale entries are replaced first, followed by the entry with the lowest construction time.

The default is 32.

This property modifies the cache created by property jaxws.JAXBContext.permStoreCostThresholdMsec


jaxws.JAXBContext.permStoreStaleThresholdHours

Set to a value, in hours, after which an entry in the JAXBContext cache that has not been accessed is considered stale. If the cache becomes full, stale entries are replaced first.

The default is 24 hours.

This property modifies the cache created by property jaxws.JAXBContext.permStoreCostThresholdMsec


jaxws.payload.highFidelity

Enable lossless transformations. When true, the Web Service runtime guarantees that the incoming message and the message at the SOAPHandler boundary are the same.

Typically, the SOAP message received by a JAX-WS SOAPHandler is not exactly the same as the inbound SOAP message. For example, the message received by the JAX-WS SOAPHandler might use different xml prefixes than the original inbound message. These subtle changes do not affect the logical interpretation of the message. However, we must add this property to the JVM settings and set the property to true if messages at the SOAPHandler boundary must be exactly the same as the incoming messages. For example, the Canonicalization Specification (C14N) requires that the prefix names are preserved.

We should only use this property if your SOAP requests access the contents of a soapenv:Body element within your SOAPHandlers. Setting the property to true might degrade Web Service runtime performance.bprac

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.provider.interpretNullAsOneway

If we have a JAX-WS web service that defines a Provider-based endpoint using the javax.xml.ws.Provider annotation and a WSDL file is not specified, we can use this custom property to control how the JAX-WS runtime environment behaves when the Provider returns a null value from the invoke() method. By default, the runtime environment will send back a response that consists of a SOAPEnvelope containing an empty SOAPBody element.

If set to true, whenever the Provider implementation returns a null value and a WSDL file is not defined, the runtime environment interprets the null value returned from the Provider implementation as a request-only operation so that no response is returned. As with all request-only operations, some qualities of services, such as WS-Transactions, will not be available.

If the javax.xml.ws.WebServiceProvider annotation specifies a WSDL value and the WSDL defines a request and response operation, the JAX-WS runtime environment always returns a response that consists of a SOAPEnvelope containing an empty SOAPBody, regardless of the setting of this property.

The default is false.

We must set this property to true for each server that requires a change in the default value.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.runtime.inheritedImplMethodsAccessible

Revise the web service runtime to allow inherited methods to be invoked. This behavior change is enabled by setting the property to true.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.runtime.restrictStaticWebmethod

Prevent exposure of static operations. When true, the JAX-WS runtime prevents the exposure of static operations.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.share.dynamic.ports.enable

Specify the visibility of dynamic ports across JAX-WS web services.

By default, dynamic ports are visible only to the instance of the service that created the port. Set to true to share dynamic ports across web services.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.soapfault.local.exceptions.disable

Use the jaxws.soapfault.local.exceptions.disable property to prevent locally occurring exceptions on a JAX-WS client from being treated as a SOAPFault. By default, if a JAX-WS client encounters a local exception, a SOAPFault is created for the exception. An example of a local exception is a ConnectException caused by an invalid host or port. The relevant JAX-WS application handlers handleFault methods are called with the SOAPFault. Then a SOAPFaultException is thrown back through the JAX-WS client's invoked method.

By setting this property to true, local exceptions create an empty message. The relevant JAX-WS application handlers handleMessage methods are called with the empty message, then a WebServiceException is thrown back through the JAX-WS client's invoked method. This was the behavior in previous releases.

The default is false.

If we decide to use this custom property, specify it as an application server JVM custom property.


jaxws.useSafeIPC

Set to true on application servers if errors occur in JAX-WS web services when the enableInProcessConnections property is set to true in the Web Container. This might happen when web services applications that call each other cannot safely share a single thread. Setting this property to true causes the applications to run on separate threads.

The default is false.


jdk.corba.allowOutputStreamSubclass

Set to true to ensures that the org.omg.CORBA_2_3.portable.OutputStream can be subclassed.

Applications running with a security manager might experience a dip in performance because of the additional security checks that are now performed to secure the org.omg.CORBA_2_3.portable.OutputStream default constructor when a security manager is installed. These additional security checks might cause incompatibilities with existing application deployments. Adding this property to the JVM settings and setting it to true prevents these incompatibilities from occurring.

This property can be set at either the application server, node agent, or deployment manager level, but is usually specified at the application server level.


localWebServerUseNodeSync

When the web server and plug-in are on the same system as the deployment manager, the propagation of the web server plug-in configuration file, plugin-cfg.xml, is usually done by a simple file system copy from one directory to another. If a node agent exists on the same system, a local managed node, we can force the deployment manager to propagate the plug-in configuration to the node agent. Use a node synchronization instead of the default file system copy method.

Go to the custom properties for the Deployment Manager JVM process by selecting...

...and add the localWebServerUseNodeSync property.

The correct value to use for this property is the name of the local node associated with the web server definition, as shown in the following example:

If multiple web server definitions are associated with multiple local nodes on the same system as the deployment manager, specify multiple node names with a semicolon as the delimiter between them, as shown in the following example:

Restart the deployment manager for the property to take effect.

Now whenever you propagate a web server plug-in, the deployment manager syncs a node to copy the plugin-cfg.xml file to the local node agent. The node agent then copies the file to the plugins/config/webservername directory. This method is the same as propagation to a remote managed node.


ODCClearMessageAge

Establish a length of time, specified in milliseconds, after which an ODC message is removed from the bulletin board, even if the receiver has not acknowledged the message. Specifying a value for this property helps prevent the build up of messages that, for some reason, do not get acknowledged.

We can specify any positive integer as a value for this property, but a value of 300000 (5 minutes) or higher is recommended to avoid premature removal of messages.

The default is 300000 milliseconds.


ODCInit.disabled

Set to true to disable the communication between processes for the On Demand Configuration (ODC) component, and for all local ODC processing.

The on demand configuration component is used when deploying Web services-based applications, and when using a WAS Proxy Server to handle requests. The on demand configuration component is enabled or disabled on a cell-wide basis. Therefore, if your topology contains any proxy servers, or any web services based applications, we should not disable the on demand configuration service.

If we are running in a large topology environment where Web services-based applications are not deployed, or WAS Proxy Servers are not used to handle requests, the on demand configuration component is not utilized, and we can set this property to true. Setting this property to true disables the on demand configuration component, which will reduce network bandwidth and CPU utilization.

The default is false.


org.apache.aries.blueprint.header.mandatory

When set to true, bundles with blueprint must have a blueprint header. This allows apache aries to avoid expensive scanning when there is no blueprint header.


org.apache.axiom.attachments.tempfile.expiration

If excessive accumulation of temporary files of the form AxisXXXXXX.att occurs, set this property to a value in seconds after which the JAX-WS runtime should delete these temporary files used for storing MTOM attachments.

The default is 0. Files are deleted when the JVM exits.


org.apache.el.parser.SKIP_IDENTIFIER_CHECK

Us this property to relax the checking that occurs for EL variable identifiers. The relaxed checking behavior is equivalent to the behavior observed in WAS versions prior to v8.0.

Starting with v8.0, the checking of EL variable identifiers is more strict. The checking process now checks for Java reserved keywords as well as reserved EL keywords. Prior to v8.0, the checking process only checked for reserved EL keywords.

If any variable identifier used in a JSTL/EL script includes any of the reserved JSP keywords, the variable identifier will fail to translate, resulting in an exception. The preferred method for handling such an exception is to modify the JSTL/EL code to eliminate the usage of the reserved keywords as variable names. However, if this is not possible or practical, set this property to true to relax the level of checking that occurs to the pre-v8.0 level.

A list of reserved JSP keywords can be found at http://docs.oracle.com/javaee/5/tutorial/doc/bnahq.html#bnail

org.apache.taglibs.standard.xml.accessExternalEntity

Set to allow access to external entities in JSP files when using the <x:parse> and <x:transform> tags.

This property takes values such as the following values:

Assign all of the URI schemes to be granted external access and separate them with commas. Use the value all to grant external access to any URI scheme.


org.eclipse.jst.j2ee.commonarchivecore.disableZip

Allow ZIP archives to be processed as simple files.

Set to true to allow ZIP archives to be processed as simple files when scanning the files of a deployed application.

The default is false.

This property must be set as a custom property for the IBM WAS process which runs applications for which ZIP files are to be ignored.

org.eclipse.jst.j2ee.commonarchivecore.ignore.ejb.in.war

Use this property if all of the following are true:

If all of the previous conditions are true, the deployment might fail because the application gets promoted to the Java EE 6 level during deployment. v7.x implements Java EE 5. EJB beans were not introduced inside WAR files until Java EE 6. When WAS v8.0 or later finds an EJB in a WAR file, it promotes the WAR file to version 3.0 and the application to Java EE 6. When this situation happens, the application cannot be deployed to a node running v7.x.

To ignore EJB beans in WAR files, and to prevent the version of the application from being upgraded, set the property to true on the deployment manager. The default is false.

Set this custom property applies the setting to all applications. To apply the setting to a specific application, edit the META-INF/MANIFEST.MF file and add the following line:

When updating the application manifest, follow line-length limitations and other constraints for the manifest.


org.eclipse.jst.j2ee.commonarchivecore.FILTERBINARIES

Use this custom property to prevent certain application files from being listed during runtime processing.

Because of new JavaEE5 annotations processing requirements, more application files are typically listed during runtime processing than are listed in previous versions of the product. The additional listing might cause applications that are migrated from previous versions of the product to start more slowly, as additional time is spent listing application files.

The default is not set.

If we decide to use this custom property, specify it as an application server JVM custom property.


org.eclipse.jst.j2ee.commonarchivecore.ignore.jee6.annotation

Use this property if all of the following are true:

If all of the previous conditions are true, the deployment might fail because the application is promoted to the Java EE 6 level during deployment. WAS v7.x implements Java EE 5 and ignores Java EE 6 annotations. WAS v8.0 or later implements Java EE 6, and therefore Java EE 6 annotations are processed. This causes a Java EE 5 application containing Java EE 6 annotations to be promoted to the Java EE 6 level. After the application is promoted, WAS v8.0 or later does not deploy the application to a node running WAS v7.x.

To ignore the Java EE 6 annotations, and to prevent the version of the application from being upgraded, set the property to true on the deployment manager. The default is false.

Set the custom property applies the setting to all applications. To apply the setting to a specific application, edit the META-INF/MANIFEST.MF file and add the following line:

When updating the application manifest, follow line-length limitations and other constraints for the manifest.


org.eclipse.jst.j2ee.commonarchivecore.ignore.jee7.annotation

Use this property if all of the following are true:

If all of the previous conditions are true, the deployment probably fails because the application is promoted to the Java EE 7 level during deployment. WAS Versions 7.x and 8.x implement Java EE 5 and Java EE 6 respectively. WAS v9.x implements Java EE 7, and therefore Java EE 7 annotations are processed. This causes a Java EE 5 or Java EE 6 application containing Java EE 7 annotations to be promoted to the Java EE 7 level. After the application is promoted, WAS v9.x does not deploy the application to a node running v7.x or 8.x.

To ignore the Java EE 7 annotations, and to prevent the version of the application from being upgraded, set the property to true on the deployment manager. The default is false.

Set the custom property applies the setting to all applications. To apply the setting to a specific application, edit the META-INF/MANIFEST.MF file and add the following line:

When we update the application manifest, follow line-length limitations and other constraints for the manifest.


org.eclipse.jst.j2ee.commonarchivecore.ignore.web.fragment

Use this property if all of the following are true:

If all of the previous conditions are true, the deployment might fail because the application gets promoted to the Java EE 6 level during deployment. WAS v7.x implements Java EE 5. Web fragments were not introduced in WAR files until Java EE 6. When WAS v8.0 or later finds a web fragment, it promotes the WAR to version 3.0 and the application to Java EE 6. When this happens, the application cannot be deployed to a node running WAS v7.x.

To ignore web fragments, and to prevent the version of the application from being upgraded, set the property to true on the deployment manager. The default is false.

Set this custom property applies the setting to all applications. To apply the setting to a specific application, edit the META-INF/MANIFEST.MF file and add the following line:

When updating the application manifest, follow line-length limitations and other constraints for the manifest.


org.eclipse.jst.j2ee.commonarchivecore.openAllArchivesTrue

Set the server to expand all archives.

To enable expansion of non-standard archives during deployment, set the property on the Application Server process involved with the deployment. If we are using a Deployment Manager, set the property on the Deployment Manager process.

To enable expansion by the earExpander script, set the property as a Java Custom property by editing the earExpander script.

The default is false.

This property is not applied to JARs within JARs. JARs within JARS will not be expanded, even with the property set to true. All JARs in EAR files and all JARs in RAR files are active. The processing of JARs in EAR files and JARs in RAR files is not affected by the custom property.


org.eclipse.jst.j2ee.commonarchivecore.PM62467.Disabled

Specify the behavior that occurs when an archive entry path contains a value that is not allowed.

When an application is deployed in WAS, the contents of the application archive and module files are extracted to the installedApps directory of the application server profile using the files' archive entry paths. Application files must be extracted to the installedApps directory, but if a file's archive entry path contains the value ../, the archive files could be extracted to another directory. If this custom property is false and the archive entry path contains the value ../, an ArchiveRuntimeException occurs and archive processing stops. Set to true to log a warning message and continue deploying the application.

The default is false.

If we decide to use this custom property, specify it as a JVM custom property on the deployment manager node and the application server.


overrideAutoProp

Use this custom property to propagate the plugin-cfg.xml to both the remote node repository and the remote web server location.

When true with manual propagation, the plugin-cfg.xml is propagated to BOTH the remote node repository and the remote web server location. When false with manual propagation, the plugin-cfg.xml is propagated to ONLY to the remote node repository and NOT to the web server location.

The default is false.

If we decide to use this custom property, specify it as a node JVM custom property.

Once this property is set for the node, we must synchronize the change to the node. Setting this property does require you to stop and start the node so that the setting takes effect.


plugin.syncdisabled

Disable the node synchronization called by the web server plug-in configuration propagation.

When true, web server plug-in configuration changes are not automatically synchronized across the node. This means any web server plug-in configuration changes we make are not propagated to the web server until we do a manual synchronization.

The default is false.

If we decide to use this custom property, specify it as a node JVM custom property.


threadpool.maxsize

Control the number of threads that can be included in a newly created thread pool. A dedicated thread is created to start each application server JVM. The JVMs with dedicated threads in this thread pool are the JVMs that are started in parallel whenever the node agent starts.

We can specify an integer from 0 - 5 as the value for this property. If the value we specify is greater than 0, a thread pool is created with that value as the maximum number of threads that can be included in this newly created thread pool. The following table lists the supported values for this custom property and their effect.

threadpool.maxsize value Effect
Property threadpool.maxsize is set to 0 or not specified. The node agent starts up to five JVMs in parallel.
Property threadpool.maxsize is set to 1. The node agent starts the JVMs serially.
Property threadpool.maxsize is set to an integer value between 2 and 5. The node agent starts a number of JVMs equal to the specified value in parallel.

For example, suppose the node agent has 10 JVMs that are set as running state, which means they are started whenever the node agent starts. If we specify 3 for this property, whenever you stop and start the node agent, only three of the 10 JVMs are started in parallel when the node agent starts.

This property is not specified by default. If we decide to use this custom property, we must specify it as a node agent JVM custom property.


(ZOS) was.xcfmonitor.enabled

Enable the use of the z/OS Cross-system Coupling Facility (XCF) for monitoring application server status. When set to true, node agents can use XCF to monitor their application servers, application servers can use XCF to monitor their node agents, and an administrative agent server can use XCF to monitor its registered application servers. When false, the TCP/IP pinging method is used to monitor application server and node agent status.

The default is false.


webservices.unify.faults

Use the webservices.unify.faults property to enable SOAP Fault unification for JAX-WS and JAX-RPC. By default, the web service runtime environments (both JAX-WS and JAX-RPC) unify all faults generated by the runtime environment to a single type of fault containing a faultcode of Server and a faultstring of Internal Error. The faults do not contain any additional information identifying the actual cause of the fault. The unification of faults results in a more secure system, preventing detailed information regarding why inbound message processing failed from being returned to message senders.

The default value for this property is true, which causes faults to be unified. If the applications require fault details, then we can set this property to false to disable fault unification, allowing detailed information to be returned in faults.

Regardless of the property settings, the following situations might appear:


wink.client.readTimeout

Specify how long the RestClient object waits (in milliseconds) for a response to requests before timing out. A value of 0 means that the client waits for an unlimited amount of time and does not timeout. The default is 60,000 milliseconds.


wink.client.connectTimeout

Specify how long the RestClient object waits (in milliseconds) before timing out when attempting to connect to the target resource. A value of 0 means that the client waits for an unlimited amount of time and will not timeout. The default is 60,000 milliseconds.

For performance reasons, IBM recommends configuring servers to use the High Performance Extensible Logging (HPEL) log and trace infrastructure
  • Custom property settings
  • Enable static routing for a cluster
  • Configure inbound transports
  • Configure SOAP over JMS message types
  • Tune the IBM virtual machine for Java
  • HTTP transport custom properties for web services applications