Unable to re-subscribe same session after journal exception

Solution Verified - Updated -

Issue

When Java client is dropped by the broker due to journal error (i.e. Enqueue capacity threshold exceeded) and tries to re-subscribe the same session, it is bounced with error "session already subscribed".

This error might affect any client that re-subscribes to the same session after the connection is lost.

Environment

  • MRG Messaging

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.