Hello,

I am trying to showcase an example where a dispatch router instance is used
as medium for AMQP based point-to-point messaging between a client and a
server.

In my example, the server creates a JMS consumer on a queue and the client
sends messages to it. I noticed that as soon as the server creates the
consumer the destination is created on the dispatch side and it appears on
the *qdstat* output. This made me think that the dispatch could be easily
flooded with consumer creation requests on random queues. My question is
thus, is there any way to prevent automatic creation of destinations on the
dispatch side and assign this permission to authorized services only?

Thanks!
Rawad

-- 
Rawad.

Reply via email to