[backport camel-4.22.x] CAMEL-24591: camel-seda - Re-register released queue reference on route restart - #26048
Conversation
…te restart Fixes a regression from CAMEL-24408 where, after a shared queue was released, stale endpoint ref/queue fields caused a send after producer route restart to fail with "No queue available". Also fixes two sibling cases: consumer-first restart (pollers kept the orphaned queue) and shared queue key (restarted endpoint not re-added, so stopping the sibling removed the queue). Endpoints now re-register via QueueReference.isReferenced(); each scenario has a test. Closes #26041 Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> (cherry picked from commit 3f28622)
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 477 tested, 29 compile-only — current: 477 all testedMaveniverse Scalpel detected 506 affected modules (current approach: 477).
|
Backport of #26041
Straight cherry-pick (
-x) of #26041 ontocamel-4.22.x. No conflicts; mechanical port (diff identical to the merged commit).Original PR: #26041
Original author: @JiriOndrusek
Target branch:
camel-4.22.xOriginal description
Fixes CAMEL-24591 (regression from CAMEL-24408): after a shared queue is released, stale endpoint
ref/queuefields made a send after producer route restart fail withNo queue available. Also fixes two sibling cases: consumer-first restart (pollers kept the orphaned queue) and shared queue key (restarted endpoint not re-added). Endpoints now re-register viaQueueReference.isReferenced(); each scenario is covered by a test.Claude Code on behalf of davsclaus