>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
>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
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, for example, for the first message
sent to the q
