Hi
No this is by-design and how this works. The consumer is active listening
for messages, as it can handle higher load and concurrent requests.
On Fri, Mar 8, 2024 at 10:48 AM Bálint Baráth <balintbar...@gmail.com>
wrote:
> Hello!
>
> I ran into a weird behaviour, that is not mentioned in any of the docs I
> found, and I don't know if this is the expected way it works.
>
> When I create a JMS request-reply with a shared replyTo queue, camel
> correctly creates a reply consumer with the JMSCorrelationID, and it
> successfully reads the response.
>
> However after this, even when there is no new request it leaves an active
> consumer on the reply queue, with the selector
> "JMSCorrelationID='CamelDummyJmsMessageSelector.'"
> When there is a new request this changes into a normal correlationID, but
> after the response the dummy selector returns.
>
> Is this supposed to happen, and if it is, is there a way to turn it off?
>
> I even tried to implement my own MessageListenerContainerFactor, but that
> proved to be too difficult for now.
>
> I tried with camel 4.0.4, 4.4.0, and 3.22.1, with springboot 3.2.3 and with
> springboot 2, so I tried with jakarta and javax and it's the same.
>
> I'm using tibco jms, and sending to a tibco ems queue.
>
> Route code snippet, this is all that is needed to reproduce. Configuration
> is from springboot application properties.
>
> from("direct:started")
> .setHeader("JMSReplyTo", constant("Q.replyqueuename"))
> .to("jms:queue:" + "Q.inputqueuename" + "?replyTo="+
> "Q.replyqueuename"
> +"&exchangePattern=InOut");
>
> Thanks for the reply in advance.
> Best regards,
>
> Bálint
>
--
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
