Forked Execution Properties panel
The Forked Execution Properties panel, which appears on the Runtime Management page (Manage > Runtime Management), can be used to set properties that affect how forked executions run.
The properties that you see on this panel are stored in your <installation_directory> in one or more of the following files:
-
/bin/procrunner.vmoptions
-
/bin/procworker.vmoptions
-
/bin/procbrowser.vmoptions
You can set a limited number of properties for configuring forked execution. Other properties that control the basic functionality of forked execution (such as, file encoding and Java security compatibility) are inherited from the runtime cluster or runtime cloud and cannot be modified.
Properties that you set on the Forked Execution Properties panel do not affect any customized runtime cluster or runtime cloud script files that you might have created previously (such as procrunner.ps1, procworker.ps1, or procbrowser.ps1). If you continue to use those customized scripts, you must update them manually.
Basic tab
Each of the following properties is stored in the appropriate vmoptions file—procrunner, procworker, or procbrowser.
| Display Name | Property Description |
|---|---|
| Runner Heap Size | The amount of memory that is allocated to a JVM being used for forked execution. The default is 512 MB. -Xmx |
| Worker Heap Size | The amount of memory that is allocated to a JVM being used for execution workers, which use forked execution. The default is 512 MB. -Xmx |
| Browser Heap Size | The amount of memory that is allocated to a JVM being used for those browsing connector operations that run in forked executions. The default is 512 MB. -Xmx |
Advanced tab
The following properties are stored in all three vmoptions files—procrunner, procworker, and procbrowser.
| Property Name | Property Value Default | Format | Property Description |
|---|---|---|---|
| Client Default Connect Timeout | 120000 | Milliseconds | The amount of time that the runtime cluster or runtime cloud should spend trying to establish an HTTP client connection. Increase this value if the HTTP endpoints are known to take longer than two minutes to return a response. -Dsun.net.client.defaultConnectTimeout |
| Client Default Read Timeout | 120000 | Milliseconds | The amount of time that the runtime cluster or runtime cloud should spend attempting to read data from an established HTTP client connection. Increase this value if the HTTP endpoints are known to take longer than two minutes to return a response. -Dsun.net.client.defaultReadTimeout |
| DNS Time to Live | 30 | Seconds | The amount of time that successful DNS lookups should be cached. Decrease this value if you call external hosts that experience frequent IP address changes to their DNS hostname. Entering a value of -1 seconds enables continuous caching, and entering a value of 0 seconds disables caching. -Dsun.net.inetaddr.ttl |
| Heap Dump on Out of Memory Error | Off | Check box | Specifies whether the runtime cluster or runtime cloud should automatically generate a heap dump when it encounters an Out Of Memory error. See the topic about high-volume troubleshooting. This property should be used only as directed by the Support team. -XX:+HeapDumpOnOutOfMemoryError |
| Java Library Path | Not set | String | Identifies one or more directories to be searched for native libraries. -Djava.library.path |
| Prefer IPv4Stack | Off | Check box | Specifies whether the runtime cluster or runtime cloud should use IPv4 for networking. Has been tested with IPv4. Therefore, strongly recommends turning this property on. -Djava.net.preferIPv4Stack |
| Retry HTTP Post | Off | Check box | Specifies whether an unsuccessful HTTP POST request should be resent to the server automatically. -Dsun.net.http.retryPost |
Custom tab
The Custom tab can be used to set forked execution properties that you do not see on the Basic or Advanced tabs. The tab is used primarily for adding custom properties that Support might ask you to set.
Any custom properties that you set are stored in all three vmoptions files—procrunner, procworker, and procbrowser.
Add a Property
Adds a blank Property field to the table.
Property
Used to enter a custom forked execution property. You must enter the complete property. For example, -Djava.property or -Dcom.property.
