KB Article #66245

Tuning properties related to message purging

Problem

What tuning properties are available to optimize configuration of Message Purge?


Resolution

The following tuning properties related to Message Purge can be set in <build>/conf/tuning.properties:



messagePurge.onceADay
 description: set to true if you want the purge task to run only once per day. By default, the purge task runs at the interval specified in messagePurge.Interval
 default value: false



messagePurge.onceADayHour
 description: If onceADay is true, this is the hour when the purge task runs. For example, 0 would be midnight, 6 would be 6:00am, etc
 default value: 0
 valid values: 0 - 23



messagePurge.Interval
 description: The amount of time, in minutes, between purge task startups. Only applies if messagePurge.onceADay is false
 default value: 15



messagePurge.useOracleProc
 description: If true (default), uses the Oracle StoredProcedure to perform the purge. If false, Java code is used to perform the purge.
 default value: true



messagePurge.oracleProcTimeLimit
 description: The amount of time, in seconds, that the Oracle StoredProcedure will perform its work. When this time limit is reached, the purge stops until the next interval. Only applies when messagePurge.useOracleProc is true.
 default value: 300 (5 minutes)



messagePurge.oracleProcChunkSize
 description: Used internally by the Oracle StoredProcedure. Only applies when messagePurge.useOracleProc is true.
 default value: 10000



messagePurge.Tasks 5
 description: Determines the number of tasks (threads) that will be started to perform the Java-based purge processing. Only applies when messagePurge.useOracleProc is false.
 default value: 5