IBM E02HMLL-I Implementation Guide - Page 294
Setting, CW_MEMORY_MAX, parameter, Configuring, memory, checker, thread, properties
![]() |
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 294 highlights
objects that are currently queued, but they do not poll new events. The connectors therefore reduce the number of queued business objects and thereby reduce the amount of memory in use, without using more memory to process new business objects. The connectors remain paused for a minimum amount of time specified by Connector pause time at threshold property. When the interval specified by the Connector pause time at threshold property passes, the memory checker thread examines memory usage again. If the memory usage does not exceed the upper threshold anymore then the memory checker thread starts the connectors again. If the memory usage still exceeds the upper threshold, however, the memory checker thread allows the connectors to remain paused. The memory checker thread sleeps in between its examination and state management operations for the amount of time specified by the Memory checker sleep time property. To use the memory checker thread, you must follow the instructions in the following sections: 1. "Setting the CW_MEMORY_MAX parameter" 2. "Configuring the memory checker thread properties" 3. "Further considerations" on page 284 Setting the CW_MEMORY_MAX parameter You must configure the Java parameter CW_MEMORY_MAX in the InterChange Server Express startup script to set the maximum heap memory that InterChange Server Express can use. The memory checker thread takes action based on the values of configurable properties that specify percentages of this maximum heap memory amount. You should set the CW_MEMORY_MAX parameter to the same value specified for the -mx parameter, which specifies the maximum heap size for InterChange Server Express. By default the CW_MEMORY_MAX parameter is set to same value as the -mx parameter, but if you modify the -mx parameter then you must modify the CW_MEMORY_MAX parameter accordingly. The following example is from an unmodified start_server.bat startup script for InterChange Server Express on a Windows computer: REM This is the -mx param value for the InterChange Server Express's memory heap set CW_MEM_HEAP=512 REM Start the InterChange Server Express %CWJAVA% -Djava.ext.dirs=%JRE_EXT_DIRS%;"%MQ_LIB%";"%DB2_LIB%" -Duser.home="%CROSSWORLDS%" -mx%CW_MEM_HEAP%m -DTEAgent=1200 -DCW_MEMORY_MAX=%CW_MEM_HEAP% %ORB_PROPERTY% -classpath %JCLASSES% ServerWrapper -s%SERVERNAME% %2 %3 The CW_MEM_HEAP variable is set to the value 512, and is used to set the -mx parameter, so 512 megabytes of memory are reserved for the Java heap. The CW_MEMORY_MAX parameter is set to the same value by also using the CW_MEM_HEAP variable. Note that the CW_MEMORY_MAX parameter must be proceeded by -D. Configuring the memory checker thread properties You must edit the InterChange Server Express configuration file to set the properties for the memory checker thread. These properties are exposed on the "Misc" tab of the InterChange Server Express configuration interface. For more information on configuring InterChange Server Express, see "Configuring 282 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide
![](/manual_guide/products/ibm-e02hmlli-implementation-guide-69bfebe/294.png)