C
Chris S. Hogan
Guest
The purpose of the serviceIntervals is to control how often the Corticon Server checks to see if there are updates to a decision service that need to be loaded into memory. This is from the config file: ############################################################################################################### # Intervals of time (ms) at which the Server checks for changes to: # 1. Changes in any cdd loaded to the Server by a loadFromCdd or loadFromCddDir call # 2. Changes in any cdd file including new cdds within the directory of cdds from a # loadFromCddDir call # 3. Changes in any of the Decision Services (.ccj files) loaded to the server. This is done via # a timestamp check. # # If any changes as described above are detected, the Server's state is dynamically updated # to reflect the changes. The "maintenance thead" that checks for these changes at the specified # intervals can be shutdown and restarted using: # - ICcServer.stopDynamicaUpdateMonitoringService() # - ICcServer.startDynamicUpdateMonitoringService() # # Default is 30 secs (30,000 ms) ############################################################################################################### com.corticon.ccserver.dynamicUpdateMonitoringService.serviceIntervals=30000 Generally 30 seconds is adequate for production configuration, but for demo and test environments you might prefer a shorter interval such as 1 to 5 seconds.
Continue reading...
Continue reading...