JVM Properties Reference

Properties can be passed to the Java Virtual Machine (JVM) to affect the behavior of ActiveMatrix BPM.

JVM properties are set on a BPM node using ActiveMatrix Administrator. For more information, see Configuring JVM Properties on the BPMNode.

The following table lists all of the JVM properties that can be set as a JVM argument using ActiveMatrix Administrator. Some of these properties are described in more detail in other topics. For those, links or citations are provided in the description.

Note: If you have upgraded to this version of ActiveMatrix BPM from version 4.2.0 or earlier, the following properties are not automatically set on the BPM node(s). You must add them manually:
  • com.tibco.pvm.LRUCache.proc.size
  • com.tibco.pvm.LRUCache.module.size
  • se.scriptexecutiontimeout
JVM Property Description
com.tibco.bx.lockOperation Specifies whether system-wide locking is enabled:
  • true (default) - system-wide locking is enabled.
  • false - system-wide locking is disabled.

For more information, see Configuring Locking Operation on Retry When Receiving/Retrieving a Message.

com.tibco.bx.lockOperation.ModuleName This is used in conjunction with com.tibco.bx.lockPerOperation to specify locking at the module level. If com.tibco.bx.lockPerOperation=true, this property can be set to true (to enable locking) or false (to disable locking) for the module specified in ModuleName.

If this property is set (either true or false), it takes precedence over the com.tibco.bx.lockOperation.ModuleName.PortType.OperationName (see below), if specified.

For more information, see Configuring Locking Operation on Retry When Receiving/Retrieving a Message.

com.tibco.bx.lockOperation.ModuleName.PortType.OperationName This is used in conjunction with com.tibco.bx.lockPerOperation to specify locking at the operation level. If com.tibco.bx.lockPerOperation=true, this property can be set to true (to enable locking) or false (to disable locking) for the operation specified in OperationName. The PortType must be in the form {NamespaceURI}localPort.

Note that if the com.tibco.bx.lockOperation.ModuleName property (see above) is also specified, it takes precedence over this property.

For more information, see Configuring Locking Operation on Retry When Receiving/Retrieving a Message.

com.tibco.bx.lockPerOperation If system-wide locking is enabled (that is, com.tibco.bx.lockOperation=true), this property can be used to enable finer-grained control over locking. Set this property to true, then use either com.tibco.bx.lockOperation.ModuleName or com.tibco.bx.lockOperation.ModuleName.PortType.OperationName to specify locking at the module- or operation-level.

For more information, see Configuring Locking Operation on Retry When Receiving/Retrieving a Message.

com.tibco.bx.lockPerSignal If signal definition locking is enabled (by setting com.tibco.bx.lockSignal=true), this property can be used to enable finer-gained control over locking. Set this property to true, then use either com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion or com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion.signalName to enable signal locking at the application- or signal-level.

For more information see, Locking of Signal Definitions.

com.tibco.bx.lockSignal Specifies whether locking is enabled on signal definitions.

Default = true

For more information see, Locking of Signal Definitions.

com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion If locking per signal is enabled (by setting com.tibco.bx.lockPerSignal=true), this property can be used to enable signal locking at the application level, as follows:

com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion

For more information see, Locking of Signal Definitions.

com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion.signalName If locking per signal is enabled (by setting com.tibco.bx.lockPerSignal=true), this property can be used to enable signal locking at the signal level, as follows:

com.tibco.bx.lockSignal.SignalAppName.SignalAppVersion.signalName

For more information see, Locking of Signal Definitions.

com.tibco.pvm.LRUCache.proc.size Maximum number of process definitions in the 'least recently used' cache (LRUCache). See Configuring LRUCache Size for Process Definitions and Modules for more information.
com.tibco.pvm.LRUCache.module.size Maximum number of modules in the 'least recently used' cache (LRUCache). See Configuring LRUCache Size for Process Definitions and Modules for more information.
se.scriptexecutiontimeout Maximum amount of time (in seconds) that a process script can take to execute before timing out. On a distributed ActiveMatrix BPM system, you must set the property on every BPMNode in the system.

Default = 60

If a script takes longer to run than the specified timeout value, the process instance halts and the following error is written to the BPM log file: 

Script execution took more than se.scriptexecutiontimeout specified timeoutValue seconds.

If the property is removed or set to zero, a process instance will wait indefinitely for a script to complete.

Configuring JVM Properties on the BPMNode

JVM Properties are configured using TIBCO ActiveMatrix Administrator. Use the following procedure to add a new property, delete an existing property, or modify the value of an existing property.

  1. In ActiveMatrix Administrator, select Infrastructure > Nodes.
  2. In the Nodes list, select BPMNode.
  3. In the lower pane, select the Configuration tab.
  4. Select the JVM Configuration link.

    The Properties section lists the existing JVM properties defined for the BPMNode. From this section, you can:

    • Add a new JVM property by clicking Add, then entering the name and value of the property.
    • Delete an existing JVM property by selecting the property in the list, then clicking Delete.
    • Modify the value of an existing JVM property by selecting the property in the list, then changing the value in the Value field.
  5. Click Save.
  6. Stop, then restart the BPMNode to have your changes take effect:
    1. Select the BPMNode in the Nodes list.
    2. Click Stop.
    3. When the Node State column shows that the node is stopped, click Install or Sync.

      This applies the configuration changes.

    4. Click Start.