activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Problem with Selector
Date Tue, 19 Jan 2010 17:40:07 GMT
I wonder if your issue is related to the pageSize, default 200, the amount
of messages that the broker will keep in memory for a destination. If your
selection criteria matches a message further down the queue than the
pageSize it will not be dispatched till those ahead of it in the queue are
consumed.

On trunk, or 5.3.0, with a prefetch=0 and a selectable message in the page
window, a receive(timeout)  will work reliable assuming no network glitches.
To make it more deterministic, use of asyncDispatch==false for your consumer
will also help.



2010/1/18 akos <akos.baraz@p92.hu>

>
> Hi, are there any news on this issue? Any low level method maybe?
> receiveNoWait and receive(timeout)  both can return null even if the queue
> contains selectable messages. It makes no sense to rely on these methods.
> --
> View this message in context:
> http://old.nabble.com/Problem-with-Selector-tp19157015p27212570.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message