Fix JMS dur sub reconnection issue in MI cluster #4056
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Resolved an issue in the MI cluster scenario where JMS durable subscribers failed to reconnect during rescheduling after a database connection failure. The problem occurred due to existing open connections blocking new connections. The fix involves properly closing JMS connections when tasks are paused, ensuring clean reconnections during recovery and maintaining reliable task execution in cluster environments.
Fixes: #3652