Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix JMS dur sub reconnection issue in MI cluster #4056

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

malakaganga
Copy link
Contributor

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

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: wso2#3652
@malakaganga malakaganga merged commit 445308f into wso2:master Feb 28, 2025
7 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: JMS inbound endpoints are failing once the cluster database issue occurred with update 11162 (U2 102)
2 participants