You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/01/23 16:47:00 UTC
[jira] [Commented] (CAMEL-17540) CamelJms Request Reply QueueReplyManager is coupled with DefaultMessageListenerContainer
[ https://issues.apache.org/jira/browse/CAMEL-17540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480672#comment-17480672 ]
Claus Ibsen commented on CAMEL-17540:
-------------------------------------
And the JMS component has a lot of options you can configure, read the doc please
> CamelJms Request Reply QueueReplyManager is coupled with DefaultMessageListenerContainer
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-17540
> URL: https://issues.apache.org/jira/browse/CAMEL-17540
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 3.x
> Reporter: Ashutosh Vaish
> Priority: Minor
>
> We are using CamelJMS to connect with IBM MQ. We are doing request-reply over JMS. It was identified that our camel app is continuously polling the reply queues even when a unit of work was completed. I found that QueueReplyManager is coupled with DefaultMessageListenerContainer.
> CamelJMS allows consumerType for JMS consumer to be Simple/Default/Custom. Why was it decided to use DefaultMessageListenerContainer for QueueReplyManager? Can we give a consumerType choice for this pattern too ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)