The other way would be to use the “pull” method to get messages from a queue and use clojure agents to handle the dispatching so you could tie a thread to a queue.
On Jan 2, 2014, at 11:52 AM, Michael Klishin <mklis...@gopivotal.com> wrote: > On 2 Jan 2014, at 20:50, Alexander Kehayias <alex.kehay...@gmail.com> wrote: > >> As a quick hack, I suppose I could always launch multiple instances of my >> app on the same box or spin up some new servers. >> >> Is this a feature (independent executor pools per channel) that you think >> could be generally useful? It would prevent one queue consumer from blocking >> another due to the shared thread pool being saturated by tasks from a >> particular queue. > > This is how RabbitMQ Java client is designed. > > You can dispatch deliveries to other executors if there’s a clear way to > group them. > -- > MK > > Software Engineer, Pivotal/RabbitMQ > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "clojure-rabbitmq" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojure-rabbitmq/TxonGAQAr9Q/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojure-rabbitmq+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
