Add idle timeout–based connection eviction to JMS transport connection caching

[SanojPunchihewa]

Current Limitation

JMS transport currently lacks a mechanism to evict stale connections from the connection pool. Cached JMS connections can remain in the pool indefinitely, even if they have been idle for a long period or closed by the broker/network. When such a stale connection is reused, it may lead to unexpected connection failures, message consumption issues, or retries at runtime.

Suggested Improvement

Introduce an idle timeout configuration for JMS transport connections

Version

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!