My webMethods Server 10.5 | My webMethods Server Webhelp | Administering My webMethods Server | My webMethods Administrator Functions | My webMethods Server Clustering | Modifying Resource Locking Settings for a Cluster
 
Modifying Resource Locking Settings for a Cluster
When installing additional components in a My webMethods Server cluster, cluster nodes obtain database locks on the resources that get updated. Component installation might require a particular resource to remain locked for a significant amount of time. To ensure that concurrent attempts to lock a resource between cluster nodes do not result in timeouts, you can configure the lock validity and wait times, using the following additional JVM parameters in the custom_wrapper.conf file for My webMethods Server:
com.webmethods.task.lock.max.time
com.webmethods.task.lock.max.wait.time
*To modify the resource locking settings for a My webMethods Server cluster
1. Shut down My webMethods Server.
2. Open the custom_wrapper.conf file in a text editor.
You can find the file at the following location:
Software AG_directory \profiles\MWS_serverName\configuration
3. In the custom_wrapper.conf file, specify the time limits for resource locking and lock waiting by adding the following additional parameters:
The following table lists the additional JVM parameters that configure resource locking for a cluster:
Parameter
Description
-Dcom.webmethods.task.lock.max.
wait.time=time_in_milliseconds
The maximum amount of time in milliseconds for which a node can wait to acquire a lock on a resource. The default value is 300000 (5 minutes).
-Dcom.webmethods.task.lock.max.
time=time_in_milliseconds
The maximum amount of time in milliseconds for which a node can lock a resource. The default value is 300000 (5 minutes).
4. Save the custom_wrapper.conf file and restart My webMethods Server.
For more information about how to set additional JVM parameters in the custom_wrapper.conf file, see Configuring JVM Settings for My webMethods Server.