> ActiveMQ provides no means to guarantee that a producer will fail to > deliver > a message when there are no consumers interested in the message. It is > actually designed more for cases of consumers being away and returning at a > later time. > > Perhaps. But I think the advisory queue message
ActiveMQ.Advisory.NoConsumer.Queue … actually solves my problem. If a producer creates a queue, and no one is consuming, I’ll just create a new consumer once I get the advisory message about the queue. This is actually how I do it *now* except I was listening to NEW queues… I’ve actually gotten a lot of use out of the advisory queue system. > As you noted correctly, ActiveMQ automatically recreates destinations every > time they are needed, so even if they were GC'ed, they would just be > automatically recreated when a producer posted a message. > Yes. And in my case, I think that’s ok. I might actually write up a blog post about this design. It’s novel but AMQ actually does seem to be working out well for us without the limitations you describe due to advisory messages. Kevin -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
