Hi What version of Camel do you use?
And are you always using temporary "private" dynamic queues for request/reply schenarious? Isnt there an overhead of some sorts on rabbitmq side if you need to have a new queue per message? Well regardless if that is a common practice, we can look into a way of configuring camel-rabbitmq to allow to stop the reply listener when a message is received or something. On Mon, Jul 2, 2018 at 1:10 PM, Nataraj Basappa <n5j....@gmail.com> wrote: > Hi All, > I’m relatively new to Camel and RabbitMQ and seeing issue similar to the > one reported here - http://camel.465427.n5.nabble.com/Apache-Camel- > RabbitMQ-consumers-leaves-back-extra-threads-running-tt5804994.html > We have spring boot application that uses RabbitMQ in Request/Response > mode through Camel RabbitMQ Component. Functionally application works as > expected but the issue is the threads that are being created for every > request. Number of connections and hanging RabbitMQ Consumer increases > every-time a request passes through RabbitMQ component. I started to use > the connectionFactory with assumption that connection pooling would with > executor service would decrease the threads but that seems not to have much > benefit. > > Is there anything else I should be looking at to iron out the issue? > Attached is a screenshot and one obvious thing that pops out is there is > always connection pair one for IPV4 and other for IPV6. > > Second issue I think is that consumer (dynamic reply queue) hangs around > and hogs the thread. Not sure how to close it as the dynamic queues are > created as part of Request/Response called from Camel multicast. > — > Regards, > Nataraj Basappa > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
