On Mon, Oct 29, 2012 at 12:30 PM, anaCortes <anquiroe...@hotmail.com> wrote: > Hi Claus, > > thank you for your quick answer. > > With the option to do more frequent polling, do you mean the receiveTimeout > option? >
Yes. > We are using this option to 250, so this should poll messages every 250 ms. > I don´t understand why some messages are always stuck on the reply queue if > the next messages are sent every more than 1 sec and this option is set to > 250 ms. Then the stuck messages should be taken from the queue. > The messages should be consumed if its JMSCorrelationID matches a id that was sent from a request. > How are the messages from the reply queue taken/choosen? > It uses JMSSelector to match which messages to pickup as reply messages, that matches JMSCorrelationID set on sending the request. It builds a JMSSelector query from this code https://svn.apache.org/repos/asf/camel/trunk/components/camel-jms/src/main/java/org/apache/camel/component/jms/reply/MessageSelectorCreator.java You can enable some TRACE logging to see the query. > Thanks. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-consume-all-the-messages-tp5721700p5721724.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
