System properties
The propertyManager set command sets properties that modify the behavior and characteristics of the server. Depending on the scope of the specific property, the values are applied to the entire system, all solutions, all agents, or all aggregates.
You can also manage these properties by using the GlobalPropertiesMXBean: com.ibm.ia.runtime.management.GlobalPropertiesMXBean. For more information, see GlobalPropertiesMXBean.
The following table lists system settings that are determined by the value of system properties.| Property | Description | Default value |
|---|---|---|
| agentDisableSaveState | Set this property to true to conserve memory resources if all the rule agents are stateless. When the property is enabled, the state of rule agents is not saved, so rule agents that are stateful do not operate correctly. | false |
| debugPort | Indicates one or more ports that the server monitors for connections from a test driver instance. The value is a single port, or a range or ports, which matches the httpport property as specified in the testdriver.properties file. | none |
| engineCacheSize | Determines the size of the rule engine caches. There is a cache for each partition. | 100 |
| eventCacheSize | Determines the size of the event object cache. There is one cache for each Node (JVM). | 1000 |
| entityCacheSize | Determines the size of the entity object cache. There is one cache for each partition. | 1000 |
jobHistoryTTL |
Determines how long job histories are retained. Specify a value of 0 or more. A value of 0 means that job histories are retained forever. You can set a value to save memory space and remove unwanted job histories. | 604800 seconds (7 days) |
| LogInitialSuppressionPeriod | Defines the time period between the first and second suppression reports. The period is doubled each time that a report is produced until the period between each report reaches the value that is defined by LogMaxSuppressionPeriod. | 5000 |
| LogMaxSuppressionPeriod | Defines the maximum period between suppression reports. | 30000 |
| LogMaxTrackedMessages | Defines the maximum number of messages that can be suppressed at any one time. When the maximum number of tracked messages is reached, new log messages that surpass the threshold are suppressed and the oldest messages make way for them. | 50 |
| LogSuppressionThresholdPeriod | Defines the time period over which log messages are counted. A log message rate is calculated from the value of the log threshold and the time period for the threshold. When the message rate is deemed too high, all subsequent messages are suppressed. Messages are produced again only when the rate falls to an acceptable volume. | 20000 |
| LogSuppressionThreshold | Defines the number of occurrences of any log message that is permitted in a specified time period. The value of this property determines the number of times a log message is produced before it is suppressed. | 10 |
| maxAgentTransactionRetries | Sets the number of times an agent retries a transaction before an error is reported. If you modify the default value, the minimum value is 2. | 5 |
| maxEventProcessingThreads | Indicates the number of agents that can run concurrently on the server. The value must be 10 to 20 times the number of CPU cores available on the server. | 100 |
| maxRecursionCount | Indicates the number of times an emitted event type that is bound to the same entity type can recur in the same event chain. | 1 |
| solutionAutoStart | Set the value to true to activate solutions automatically upon deployment. In a production environment with multiple servers, set the value of the solutionAutoStart property to false so that you can install a solution on each server before you activate the solution. | true |