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
consu
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-tp19
Sorry about opening up an old thread, by I've got all the same fustrations as
Jecsiac with this issue.
How can I write a deterministic system to return a message if it exists on a
queue, or null if it doesn't exist. How long should I wait, a second, a
minute, an hour? What if I have a million m
>It seems to be provider specific. Many JMS providers will treat
>"Receives the next message if one is immediately available" literally
>- i.e. not to wait for a request/response with the broker to check if
>there is a message available for processing. This is what ActiveMQ
>does and a number of o
It seems to be provider specific. Many JMS providers will treat
"Receives the next message if one is immediately available" literally
- i.e. not to wait for a request/response with the broker to check if
there is a message available for processing. This is what ActiveMQ
does and a number of other J
>receiveNoWait() is not meant to wait for a message to arrive. In
>ActiveMQ creating a receiver does not block until messages are
>received.
>i.e. its not really JMS compliant to use receiveNoWait() and not
>expect nulls to come back if you've not really left much time for the
>JMS provider to ac
Thanks a lot at first. No, I'm not trying to do request/response over JMS. I
use receiveNoWait() because I need to return immediately when there's no
message in the queue. I'll try receive(some time) later. However, it is so
regret that different JMS providers behave so differently... My codes go
BTW are you trying to do request/response over JMS - is that why
you're numbering your messages and trying to receive a specific one
back?
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
2008/8/26 James Strachan <[EMAIL PROTECTED]>:
> 2008/8/26 Jecsiac <[EMAIL PRO
2008/8/26 Jecsiac <[EMAIL PROTECTED]>:
>
> Hi, I have a problem when using selector in ActiveMQ 5.1.0.
>
> I set a property named 'SomeId' on every Message sent to the queue, and
> every Message has a different value of that property (the value is just the
> order of the message sent to the queue,
