Configuring Multi-threaded Continuous Monitoring for Sonatype Lifecycle

This guide provides instructions for sizing and enabling multi-threaded Continuous Monitoring (CM) for Sonatype Lifecycle (IQ Server). Multi-threading can significantly reduce CM processing time, helping CM complete within a desired execution window while maintaining system stability and performance.

The CM job evaluates application policy activity daily (defaulting to 12:00 AM). While CM is single-threaded by default and runs on a single node in High Availability (HA) environments, multi-threading can significantly reduce total processing time. However, it requires careful configuration to avoid excessive CPU utilization or service throttling.

Analyze the clm-server.log to identify the single-threaded baseline. Search for the following log patterns:

To verify the configured thread pool at startup, look for a line similar to:

com.sonatype.insight.brain.policy.evaluator.PolicyMonitor - insight.threads.monitor pool-size: 1

To ensure CM completes within a 20-hour window (leaving a 4-hour operational buffer), calculate the thread pool size using the total single-threaded duration extracted from the logs.

Formula:

OptimalThreadPoolSize = ceil( TotalTimeInMs / (20 × 60 × 60 × 1000) )

Example

Log: Finished policy monitoring applications in 437824876 ms
Allowed time (20 hours) = 72,000,000 ms
Optimal pool size = ceil(437,824,876 / 72,000,000) = 7
=> java argument: -Dinsight.threads.monitor=7

Paste this into Bash/Zsh to extract the <N> ms value from your log line and compute the suggested thread pool size.

calculate_thread_pool_size() {
  local log_line="$1"
  local buffer_hours=4
  local total_hours=24
  local allowed_hours=$((total_hours - buffer_hours))
  local allowed_time_ms=$((allowed_hours * 60 * 60 * 1000))
  local total_scan_time_ms
  local pool_size

  total_scan_time_ms=$(echo "$log_line" | grep -oE '[0-9]+[[:space:]]*ms' | grep -oE '[0-9]+')

  if [[ -z "$total_scan_time_ms" ]]; then
    echo "Error: Could not extract scan time from log line."
    return 1
  fi

  pool_size=$(( (total_scan_time_ms + allowed_time_ms - 1) / allowed_time_ms ))

  echo "Total scan time: ${total_scan_time_ms} ms"
  echo "Allowed scan time: ${allowed_hours} hours (${allowed_time_ms} ms)"
  echo "Optimal thread pool size: $pool_size"
  echo "java argument: -Dinsight.threads.monitor=$pool_size"
}

Example usage

log="Finished policy monitoring applications in 437824876 ms"
calculate_thread_pool_size "$log"

The thread pool size is controlled by a JVM system property set at server startup:

-Dinsight.threads.monitor=<N>