[
https://issues.apache.org/jira/browse/CAMEL-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062486#comment-13062486
]
Claus Ibsen commented on CAMEL-4202:
------------------------------------
The reason why the persistent reply to example at the nabble discussion, is
because Camel will have to use a Dummy value for JMSMessageSelector when there
is no expected replies to receive. And it thus takes 1 sec. for it to timeout,
before it can update the JMSMessageSelector with the CorrelationsIDs to receive.
We may try to suspend/resume the message listener container, but we could
potential end up with some synchronized issue where we would suspend the
listener, where as in the mean time on another thread a new message is being
send. And thus we may miss resume the listener. Therefore we end up not pulling
the message from the AMQ broker.
We should add some documentation / FAQ as the drawbacks of using persistent
queues.
> camel-jms - Using request/reply over persistent queues should be faster
> -----------------------------------------------------------------------
>
> Key: CAMEL-4202
> URL: https://issues.apache.org/jira/browse/CAMEL-4202
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.7.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/slow-reply-for-jms-component-when-url-contains-replyTo-tp4563075p4563075.html
> When using persistent replyTo queues for request/reply over JMS, then the
> ReplyManager should be faster to pickup replies.
> The default spring-jms timeout is 1 sec and it impacts the performance.
> Likewise the receiveTimeout should not be set on the reply managers as that
> does not apply here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
