2026.09.43 — 2026-09-25

Breaking

• Let plugin consumers handle several messages at once (122f07e2)

  A plugin's consume registration now states how many messages it handles at once on each serving node: RegistrationSpec.concurrency, 1 to 32. A tap takes exactly 1. Studio opens that many consumers per node, and each holds at most one unacknowledged message, so a slow plugin is handed fewer messages and the rest wait on the queue. Messages that share a group id (JMSXGroupID) stay in order at any concurrency, because the broker hands a group to one consumer. MessageRegistration reports the concurrency.

  Plugin message handlers now run on a bounded thread pool of their own (artemis-studio.plugins.messaging.max-threads, default 64 per node), so a plugin that blocks can no longer delay message capture or operator sessions.

Added

• Let plugin consumers handle several messages at once (122f07e2)

  A plugin's consume registration now states how many messages it handles at once on each serving node: RegistrationSpec.concurrency, 1 to 32. A tap takes exactly 1. Studio opens that many consumers per node, and each holds at most one unacknowledged message, so a slow plugin is handed fewer messages and the rest wait on the queue. Messages that share a group id (JMSXGroupID) stay in order at any concurrency, because the broker hands a group to one consumer. MessageRegistration reports the concurrency.

  Plugin message handlers now run on a bounded thread pool of their own (artemis-studio.plugins.messaging.max-threads, default 64 per node), so a plugin that blocks can no longer delay message capture or operator sessions.