NIFI-16287 - Ensure orderly shutdown of active and idle JMS workers

[pvillard31]

Summary

NIFI-16287 - Ensure orderly shutdown of active and idle JMS workers

This change introduces explicit lifecycle ownership for every JMS worker created by AbstractJMSProcessor, including workers currently executing onTrigger. When a processor is unscheduled or loses primary-node ownership, active and idle workers are now closed promptly. Retired workers cannot be returned to the pool or rebuilt, and worker shutdown is idempotent so concurrent lifecycle and trigger threads cannot destroy the same connection factory more than once.

The accompanying tests exercise construction and shutdown races, primary-node transitions, and bulk cleanup failures. Broker-backed tests also verify that shutdown interrupts a blocked ConsumeJMS receive, preserves redelivery when acknowledgement occurs after closure, and maintains the existing PublishJMS success and failure routing behavior during concurrent shutdown.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
• Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using ./mvnw clean install -P contrib-check
  • JDK 21
  • JDK 25

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files