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 enable the pruning of intermediate DOM nodes after the XML parse of the metadata occurs for an application.
The default value for this property is false.
Use this custom property to enable the sharing of JavaClass instances, and the conversion of expanded JavaClass and JavaMethod objects to lightweight proxies after they are used.
The default value for this property is false.
Use this custom property to generate a trace from code areas that are enabled when the com.ibm.config.eclipse.wtp.enablejemtrim custom property is set to true.
Use this custom property to generate a trace from code areas that are enabled when the com.ibm.config.eclipse.wtp.enablexmltrim custom property is set to true.
Use this property to 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 you 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 your system, you 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 value for this property is false.
<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.
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 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 custom property to specify, 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 custom property to 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.
The default value is 180.
An error occurred while stopping Server1. Check the error logs for more information.
The default value is 5000 (5 seconds).
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.
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.
For WebSphere Application Server at level, 6.1.0.21 or later, use this property to specify how you want to manage enhanced EAR files.
Use this property to 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 you 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 expands the enhanced EAR file in the app_server_root/profiles/installedApps/current_cell_name 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_name directory, where original_cell_name is the cell on which the application was first installed. If you specified the $(CELL) variable for Directory to install application when you first installed the application, installation expands the enhanced EAR file in the app_server_root/profiles/installedApps/current_cell_name 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 you set processEmbeddedConfigGlobal to false, the product does not process the embedded configuration of enhanced EAR files. However, when deploying an individual enhanced EAR file, you 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.
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 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 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 you set this custom property to true, the application server does not distribute application binaries to target nodes that contain Web server targets only.
wsadmin>$AdminApp isAppReady SuperApp ADMA5071I: Distribution status check started for application SuperApp. WebSphere:cell=IBMCell10,node=IBMNode30,distribution=true,expansion=skipped ADMA5011I: The cleanup of the temp directory for application SuperApp is complete. ADMA5072I: Distribution status check completed for application SuperApp. true
where the server_name and node_name variables are specific to your environment.
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.
After you change the value for this custom property,
you must do a full synchronization before this change is reflected
in the server.xml file on the node. If you cannot start the node agent
for the server, you must manually edit the server.xml file to change
the value of this custom property from true to false.
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.
If 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
Use this property to 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.
Use this property to 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 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 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.
Use this property to specify, in seconds, how long the web services engine should wait before reusing a one-way connection. When a one-way connection is reused to quickly, a web service operation mighty 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, startingfrom when the request is sent.
By default, this property is not set and one-way connections are reset immediately after the request is sent.
Use this property to 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 you 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 your JAX-WS application, set this property to false.
Prior to Version 6.1.0.31, if an SSL binding is attached to a JAX-WS application, JAX-WS automatically uses the system default SSL settings instead of using the SSL transport bindings.
Use this property to indicate error situations in which you 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 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.
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 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.
Use this property to indicate whether you want to log the host, port, and username of SOAP client requests. When this property is set to 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 value for this property is false.
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.
Use this property to 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 functionality for initialization.
If you are using a resource adapter that requires the availability of Connection Factory MBeans at initialization, add this property to your JVM settings and set the value to true.
The default value for this property is false.
Thread pools that are 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 this property to true if you want the server to send a message to the log file when a thread pool that is allowed to grow increases beyond its configured maximum size.
The default value for this property is false.
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.
Use this property to 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 that 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 you 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
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 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 this property is 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 value for this property is false.
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 specify whether the application server uses an actual prefix name to locate the namespace that defines of 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:
<soapenv:Fault xmlns:soapenv= "http://schemas.xmlsoap.org/soap/envelope/"> <faultcode xmlns="http://sample"> sampleFault </faultcode> <faultstring>sample text</faultstring> <detail encodingStyle=""> <sampleFault xmlns="http://sample"> ... </sampleFault> </detail> <soapenv:Fault>
<soapenv:Fault xmlns:soapenv= "http://schemas.xmlsoap.org/soap/envelope/"> <faultcode xmlns="http://sample"> sampleFault </faultcode> <faultstring>sample text</faultstring> <detail encodingStyle=""> <sampleFault xmlns="http://sample"> ... </sampleFault> </detail> <soapenv:Fault>
Both versions of this message are correctly processed by a WebSphere Application Server client. However, if you have .Net clients running on your system, and migrate a JAX-RPC application from Version 5.1, some of your .Net clients might fail if they receive the newer version of the message.
If your 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 this property is set to true, the message that the application server issues is similar to the message that was sent from a Version 5.1 application server.
The default value for this property is false.
Use this property to control the messages that display during server start up based on message type.
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.
If the amount of time required to change a configuration change is unsatisfactory, you can add the config_consistency_check custom property to your JVM settings and set the value of this property to false.
Use this property to 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 the FileServingEnabled attribute is set to true, the plugin-cfg.xml file generator automatically adds the wildcard URI mapping, /* , to the plugin-cfg.xml file, which negates the usefulness of defining unique file serving patterns.
Setting the the deactivateWildCardURIMapping property to true prevents the plugin-cfg.xml file generator from adding the /* to the plugin-cfg.xml file, and enables the plugin-cfg.xml file 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.
This property is set at the deployment manager level.
Specifies the 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 that are 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.
Specifies the maximum number of threads to maintain in the DRS thread pool.
The default value for this custom property is 100 threads.
Specifies whether the number of threads can increase beyond the maximum size that is 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 value for this custom property is false.
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 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.
The logging.properties file
is located in the <<WAS_install>>/java/jre/lib/logging.properties directory,
and can be customized as needed.
The logging.properties file
is located in the <<WAS_install>>/java/J*/lib/logging.properties directory,
and can be customized as needed.
The default setting for this property is false.
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.
Set this property to true if you want to disable the communication between processes for the On Demand Configuration (ODC) component. If you do not use ODC, setting this property to true completely disables ODC when its not being used, which reduces network bandwidth and CPU utilization.
ODC is typically used to deploy Web services-based applications, or if a WebSphere Application Server Proxy Server is being used to handle requests. If you do not use either of these functions, the on demand configuration component is not utilized and can be disabled.
The default value is false.
The JVM custom property, threadpool.maxsize, is a dedicated string used to start each application server. threadpool.maxsize controls the number of application servers that are started in parallel. You add threadpool.maxsize on the Node Agent to provide thread pool size as follows:
System Administration > Node agent > nodeagent_ name > Configuration > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties > New. Then you supply the name, threadpool.maxsize and a value.
If the value you supply is greater than 0, then a threadpool is created with that value as its maximum value. For example, if the value you supply is 3, a maximum of 3 application servers will be started in parallel. If the value you supply is 0 or less than 0, then the Node Agent behaves by launching application servers sequentially.
There is no maximum value for threadpool.maxsize. The maximum threads created will be equal to the number Application Servers. You cannot configure this value.