Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <20104341.post@talk.nabble.com>
Date: Tue, 21 Oct 2008 22:47:14 -0700 (PDT)
From: logictude <andrew@logictude.com>
To: users@activemq.apache.org
Subject: Stomp Client Hoarding Messages
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Here's the nutshell:

I have AMQ (v5.1.0) running great and my clients subscribe just fine. At
this moment I have between two and three clients connected to AMQ (queue,
FYI, not topic).

Each client reads incoming messages and checks for a keyword against the DB.
When a client does find a match it sends a simple ACK frame back to the
broker and everything is great. When there ISN'T a match, the client holds
onto the message - because there's no ACK sent back - and never releases the
message for any other client to consumer/taste/confirm.

Is there a way to drop (NO-ACK) the message so another client can pick it
up?

I've resorted to tossing the message to another queue but that doesn't scale
well for the applications we have.

Is this behavior inherent in the Stomp client only?

Please advise. There is flexibility here, it's all a matter of understanding
the limitations.

Sincerely,
andrew
-- 
View this message in context: http://www.nabble.com/Stomp-Client-Hoarding-Messages-tp20104341p20104341.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.