OutOfMemoryExceptions from the JVM can halt InterChange Server Express. To reduce such occurrences, a "memory checker" feature in InterChange Server Express can be used to pause the connectors when a predetermined level of memory usage is reached, ensuring that no new events are delivered to the connector, but still allowing it to process pending service call requests from InterChange Server Express. This can reduce memory usage. The parameters for the memory checking feature can also control the speed of event delivery to InterChange Server Express from all connectors, providing finer granularity of flow control.
Perform the following steps to implement memory checking:
CW_MEMORY_MAX
This value determines the maximum heap memory InterChange Server Express is allowed to use. It should be the same value, in megabytes, as the JVM maximum heap size specified in the startup scripts of InterChange Server Express (-mx parameter). For example:
-DCW_MEMORY_MAX=512m