You can use the administrative console to change the values of Java™ virtual machine (JVM) custom properties.
To set these custom properties, connect to the administrative console and navigate to the appropriate Java virtual machine custom properties page.
Application server |
|
Deployment manager |
|
Node agent |
|
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 your changes.
Use this custom property to support JSR-47 customized logging to write to the SystemOut stream without the format of WebSphere Application Server. The format of WebSphere Application Server 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 WebSphere Application Server, set this custom property to true.
An error occurred while stopping Server1. Check the error logs for more information.
The default value is 5000 (5 seconds).
Specifies, 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.
The default value is 180.
Specifies, in seconds, the amount of time that you want the deployment manager to wait for the extension tasks of the save operation to complete before starting the updated application.
Usually during the save operation for an application update that is being 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 you add this custom property to your 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, thereby preventing the application from becoming corrupted during the synchronization portion of the rollout update process.
The default value is 180.
Use this property to specify the time between sweeps to check for timed out beans. The value is entered in seconds. For example, a value of 120 would be 2 minutes. This property also controls the interval in the Servant process that checks for timed out beans still visible to the enterprise bean container.
The default value is 4200 (70 minutes). The minimum value is 60 (1 minute). The value can be changed through the administrative console. To apply this property, you must specify the value in both the Control and Servant JVM Custom Properties.
Use this property to indicate that you want to delete JavaServer Pages classes for all applications after those applications have been deleted or updated. The default value for this property is false.
Use this property to indicate that you want to delete JavaServer Pages classes for all applications after those applications have been deleted, but not after they have been updated. The default value for this property is false.
Use this property to indicate that you want to delete JavaServer Pages classes for all applications after those applications have been updated, but not after they have been deleted. The default value for this property is false.
The EJB container should allow for the expansion of the CMP Connection Factor 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 Fatory JNDI Name.
If the value is true, the EJB Container expands a variable when found in the CMP Connection Factory JNDI Name. If the value is set to false, which is the default, the EJB Container does not expand a variable.
Use this Enterprise JavaBeans (EJB) custom property to expand the variables used in a container-managed persistence (CMP) connection factory Java™ Naming and Directory Interface (JNDI) name.
The EJB Container should allow for the expansion of the CMP connection factory JNDI name when a JNDI name contains a user-defined Application Server variable(although V6.1 does not support the expansion of variables). You need to use this property in order to expand the variables. You can enable or disable expansion.
To enable the expansion, the property value is true. To disable, use the value false.
The default is false.
If the value is true, the EJB container expands a variable found in the CMP connection factory JNDI name. If the value is false, the EJB container does not expand a variable.
Use this property to override the default setting for the Java Virtual Machine JSP enable class reloading property. The JSP enable class reloading property is enabled by default. When the JSP enable class reloading property is enabled, the JavaServer Page (JSP) attribute reloadEnabled is automatically set to true in the ibm-web-ext.xmi file.
To disable automatic class reloading, you can manually deselect the JSP enable class reloading property, or you can set the com.ibm.websphere.management.application.client.jspReloadEnabled custom property to true. If you set this property to false, JSP class reloading is enabled.
This custom property must be set at the deployment manager level.
Use this property to specify that when any of your applications are updated, you want the binaries directory erased and the content of the updated EAR file completely extracted.
If this property is 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 a large number of files change.
Use this property to specify that when the specified application is updated, you want the binaries directory for that application erased and the content of the updated EAR file completely extracted.
If this property is 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 a large number of files change.
Use this property to specify that you want your application recycling behavior to work the same way as this behavior worked in Version 5.x of the product.
In Version 6.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 Version 5.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.
The default value for this custom property is false.
Use this property to 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 60 seconds. The amount of time that you specify 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 you are using Version 6.1.0.21 or higher.
Use this property to specify, in seconds, 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 that you specify for this property should be the maximum amount of time that 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 your applications are updated, one or more of these applications do not start when the server starts, you might have to specify a longer length of time for the rollout update function to wait before starting the server.
Use this property to to disable the promotion of resources from a server to a cluster while creating a cluster member with existing resources from that server.
Typically, when you create the first cluster member for a cluster, using either a template or an existing server, any resources that are scoped for the template or server are automatically scoped for the entire cluster. This process overrides any resources that are already defined for the cluster. If you set this property to true, resources defined for the template or server are not copied to the cluster scope if any resources are already defined for the cluster in the resources.xml file for that cluster.
Use this property to enable the controller to randomly select an initial servant from the servant pool to process a Java Management Extensions (JMX) connector requests instead of automatically assigning the request to the hot servant.
By default, when multiple servants are enabled, and an 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 a lot of 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.
Use this property to 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 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 this property to false if you want the server to run even when the node agent is not running. When this property is set to true, the federated server registers with the LSD. The default value for this custom property is true.
When you 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.
Setting 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, you do lose a potential level of failover provided by the node agents of the HAManager.
WLM processing is retained with weighted spraying of requests.
gotchaIf you cannot contact the server, check the setting for the com.ibm.websphere.network.useMultihome property to ensure it is correct. You can change the value through the administrative console. Modify the defaults by setting the value for the server, deployment manager, and node agent. You must restart the server before these changes take effect.
com.ibm.ws.cscope.maximumRetries: the number of retries to attempt before the server is allowed to shutdown. Setting '-1' indicates retry forever com.ibm.ws.cscope.retryInterval: the time between retry attempts in milliseconds
<partname env:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/ xsi:type='ns1:ArrayOf_xsd_string'> <item xsi:type='xsd:anySimpleType'>namevalue</item> </partname>
<partname xsi:type="soapenc:Array" soapenc:arrayType="xsd:string[1]"> <item>namevalue</item> </partname>
Set this property 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.
Use this property to specify, in kilobytes, the maximum size of a Web services attachment that can be written to memory. For example, if your Web service needs to send 20 MB 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 you do not specify a value for this property, the maximum memory that is used to cache attachments is 32 KB, which is the default value for this property.
Use this property to specify whether the wsjar protocol handler throws a FileNotFoundException from URLConnection.getInputStream if the URL that the class loader returns is used as the context for constructing a new URL for an entry that does not exist.
When a class loader locates a resource in a zip file, it returns a URL with a wsjar protocol handler. If that URL is used as the context for constructing a new URL for an entry that does not exist, the wsjar protocol handler typically return a null value, rather than a FileNotFoundException, from URLConnection.getInputStream. If you set this property to true, the wsjar protocol handler returns a FileNotFoundException from URLConnection.getInputStream. If a value is not specified for this property, or if this property is set to false, then a null value is returned.
Use this property to enable the product logging mechanism to compute the compute the source class and method name for a logging record. The default value for this property is false, which means that this functionality is disabled.
Setting this property to true enables this functionality. As with any functionality that increases the amount of data that is logged, there might be a performance impact if you set this property to true.
This property can only be specified if you are using Version 6.1.0.21 or higher.
Use this property to 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 you 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 value for this property is false.
By default on WebSphere Application Server Version 6 or later, a SOAP over JMS Web service message sent by the Web services gateway is sent as a JmsBytesMessage, whereas on WebSphere Application Server Version 5.1 the Web services gateway sends a JmsTextMessage.
Set this property 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.
Use this property to specify whether you want an exception to be issued if a JavaServer Page (JSP), that is using a pageContext.include() method to include a file that does not exist.
If you set this property to true, and the file specified on the pageContext.include() method does not exist, an exception is sent to the JSP. You can then code the JSP to ignore the exception, and generate the page as if the pageContext.include() method error did not occur.
If you do not specify a value for this property, or if you set this property to false, and the file specified on the pageContext.include() method does not exist, an error message is issued, and the JSP page does not display.
Specify 7bit, if you only want integers greater than 127 encoded. Specify 8bit, if you only want integers greater than 255 encoded. Specify binary, if you want encoding disabled for all integers.
The default value is 7bit.
Use this property to 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.
You 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 value for this property is false.
You can also use an application assembly tool to specify this property as a new Web service description binding entry for the port component binding, if you want to disable lazy parsing of SOAPElements on an application-by-application basis for a particular server, instead of for all of the servers that are managed by the deployment manager.
Use this property to control whether clients can ignore extra XML elements that are sometimes found within literal SOAP operation responses.
Setting this property to true provides you with the flexibility of being able to update your server code to include additional response information, without having to immediately update your client code to process this additional information. However, when this functionality is enabled, the checking of SOAP message against the expected message structure is more relaxed than when this property is set to false.
Use this property to control whether the MetaDataLoade E loadWebContainerPorts could not find any http or https ports message appears in the server error log file. This message might falsely indicate that an error occurred when a Web services application is installed across both a Web server and an application server, even though this is a valid configuration.
If you set this property to true, the MetaDataLoade E loadWebContainerPorts could not find any http or https ports message does not appear in the server error log file. If you set this property to false, the MetaDataLoade E loadWebContainerPorts could not find any http or https ports message appears in the server error log file.
Use this property to control how the Web services component handles a null character in a SOAP message. Typically, when an Lightweight Directory Access Protocol (LDAP) server indicates that it has found a null character in a SOAP message, the Web services issues a javax.xml.soap.SOAPException: org.xml.sax.SAXParseException because a null character is invalid in XML.
This is the default value, and is the value that is used if an invalid value is specified for this property. For example, if you enter IGNORE_NULL_STRING as the value for this property, the property defaults to the USE_ENCODED_XML value.
Use this property to control whether the Web services component serializes the top-level element, also referred to as the operation element, of an outbound SOAP request such that it does not have a namespace prefix. This is to property enables you to send requests to older versions of .NET.
This property should only be used with Web service clients whose WSDL binding style is document\literal\wrapped, and whose message destination is an older version .NET server. This property does not function properly if the Web service clients do not meet both of these conditions.
If you set this property to true, the Web Services component serializes the top-level element of an outbound SOAP request such that it does not have a namespace prefix. If you set this property to false, the Web Services component serializes the top-level element of an outbound SOAP request such that it includes a namespace prefix.
Use this property to control whether a port number can be left 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 you have a Web service client that needs to inter-operate 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 you set this property to true, the port number is removed from the HTTP POST request before it is sent.
The default value for this custom property is false.
Use this property to 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. The default value for this property is true.
Use this property to 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 that is 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), you should increase the size of the invocation cache.
A larger cache uses more of the Java heap, so you might also need to increase the maximum Java heap size. For example, if each cache entry requires 2KB, maximum thread size is set to 25, and the URL invocation cache size is 100; then 5MB of Java heap are required.
You can specify any number higher than 0 for the cache size. Setting the value to zero disables the invocation cache.
Use this property to disable IPv6 support. On operating systems where IPv6 support is available, the underlying native socket that WebSphere Application Server uses is an IPv6 socket. On IPv6 network stacks that support IPv4-mapped addresses, you can use IPv6 sockets to connect to and accept connections from both IPv4 and IPv6 hosts.
Setting this property to true disables the dual mode support in the JVM which might, in turn, disrupt normal WebSphere Application Server 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, except on the Windows® operating system where the default is true.
Use this property to disable IPv4 support. Setting this property to true disables the dual mode support in the JVM which might, in turn, disrupt normal WebSphere Application Server 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, except on the Windows operating system where the default is true.
Use this custom property to support configuration of JSR-47 logging by setting the property value to true. When the custom property is set to true, the logging.properties file is read upon server startup and the logging configuration for applications using JSR-47 logging is initialized based on the configuration 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 can cause an infinite loop as mentioned in the Java logging topic. The logging.properties file is located in the <<WAS_install>>/java/jre/lib/logging.properties directory and cannot be customized as needed. When the custom property is omitted or set to false, the logging.properties file is not used.
Use this property to 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.
You 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 value is 300000 milliseconds.
Use this property to specify whether a previously invalidated session ID can be used. When this property is set to true, an incoming session ID can be reused even though it was previously invalidated. Setting this property to true also prevents the checking of the persistent store, which improves performance.
The default value is true.