activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From akkij <akash.j...@coreobjects.com>
Subject destroying an asynchronous message consumer after onMessage call
Date Sat, 22 Nov 2008 15:40:03 GMT

Hi,

In our application (using ActiveMQ) we have a single Producer sending
multiple messages to the Queue & multiple Message Consumers are listening to
the Queue. The requirement is that one Consumer should only receive one
message and once done should be destroyed. Basiscally one Consumer per
Message requirement. 

We have alread tried to destroy the Consumer by closing Connection, Session,
Consumer at the end of onMessage function but the Message still remains in
the Queue and another Consumer could listen to this message again. 

If anyone could help us with this kind of scenario or let us know the way to
destroy a Consumer after it has done it's job it would be greatful.

Thanks,
Akash
-- 
View this message in context: http://www.nabble.com/destroying-an-asynchronous-message-consumer-after-onMessage-call-tp20637554p20637554.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message