Steps for controlling server memory usage

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.

Note:
The memory checker feature can also negatively affect the performance of InterChange Server Express server, and should be used with caution. First try other methods of flow control, and use the memory checker only as the last solution for memory problems.

Perform the following steps to implement memory checking:

  1. Add the following parameter to the InterChange Server Express startup script file, as a Java property parameter (-D option):
    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
    
  2. Use System Manager to customize server-memory usage by doing the following:

Copyright IBM Corp. 2004