HornetQ: non consumed messages stay pending for 60 secs after consumer close

Solution Unverified - Updated -

Issue

  • I have 10 messages in a HornetQ Queue. My client connects to the queue, creates a receiver and calls 3 times receive(), then closes (ie: the receiver, the session and the connection).

  • The client does receive 3 messages out of the 10, but the 7 remaining stay pending for 60 secs, although the client cleanly closed itself. This means that if a new client comes in, it will not be able to see the remaining messages for 1 minute. I would have expected that outside of the situation of a client crash, the 7 remaining messages would have been immediatelly available.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.1.2
    • 5.2.0
    • 6.0.0
    • 6.0.1
    • 6.1.0
    • 6.1.1

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.