Interval Controller v1.1.2

Overview

Interval Controller for Apache JMeter executes nested elements at most once per configured interval per thread, and only when the thread encounters the controller. When the interval has not elapsed, nested samplers are skipped immediately (no sleep). Sibling samplers outside the controller continue normally.

This is a Logic Controller, not a JMeter Timer and not a background scheduler. It does not wake threads on a timer.

Features

• Interval-based EXECUTE / SKIP (Variant A — no background wake-up)
• Execute on first iteration
• Interval from Execution Start or Execution Completion
• Retry on Failure, Retry Delay, Maximum Retries (0 = unlimited when retry is enabled)
• Random Jitter (Positive / Symmetric)
• Dynamic Interval expressions
• Token expiration helpers (Unix ms / Unix s / TTL seconds), Refresh Before Expiration, Force Refresh
• GUI configuration and JMX persistence
• Nested controller compatibility improvements (Once Only / Loop)

Compatibility

Component	Status
Apache JMeter 5.6.3	Verified
Java 8+ (bytecode major 52)	Verified
Java 17 (running JMeter / tests, as documented)	Verified
Windows GUI / Non-GUI	Verified
Linux Non-GUI (Docker)	Verified
Linux GUI	Not tested

Installation

1. Download jmeter-interval-controller-1.1.2.jar from this release.
2. Copy to apache-jmeter-5.6.3/lib/ext/.
3. Remove any older jmeter-interval-controller-*.jar.
4. Restart JMeter.
5. Add → Logic Controller → Interval Controller.

Artifact integrity

File	SHA-256
jmeter-interval-controller-1.1.2.jar	94F834F68B6825240C6179D15352BF693583B444B1C3F7D441CD190E5EDF591C

Also attached: SHA256SUMS.txt.

Documentation

• Repository: https://github.com/GeorgeKalyaev/jmeter-interval-controller
• docs/CONFIGURATION.md
• docs/EXAMPLES.md — including Run Authentication Once Every 10 Minutes
• examples/*.jmx

Upgrade notes

• Remove older plugin JARs before installing 1.1.2.
• JMX from 1.0.0 / 1.1.x loads with defaults for newer fields.
• Identify builds by SHA-256, not version string alone.
• Do not replace this release asset with a local rebuild when distributing 1.1.2.

Known limitations

• The controller does not wake threads on a timer; it must be encountered.
• Retry behavior is subject to Thread Group On Sample Error policy.
• Token TTL uses wall clock; unbound TTL does not force perpetual refresh.