Ahh - interesting. I am concerned with that logic because there's going to be some time between starting up a producer and starting up a consumer - and ActiveMQ provides asynchronous messaging. That use-case creates an order-of-operations dependency over an asynchronous messaging layer.
Also, it is important to avoid having a Queue for which no consumers are active - that can easily lead to a slow-consumer problem, which is the number 1 cause of problems for ActiveMQ use in my experience. Are the consumers somehow untrusted to consume from the right Queues? -- View this message in context: http://activemq.2283324.n4.nabble.com/why-consumer-need-to-create-Queue-to-consume-it-tp4690517p4690678.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
