When we set prefetch=none, consumer.receiveNoWait() -Does not seem to work? What is the reason?
Article ID: KB0091508
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
The two are "incompatible". If we set the prefetch=none on a queue, we should not attempt to use receiveNoWait().
The receiveNoWait() means that the client does not want to wait if message is not immediately available. So this works
well with prefetched messages since they would already be in the client's internal queue. When setting prefetch=none,
the user instructs the client API to fetch individual messages. But then, the nature of receiveNoWait() causes it to return
if it would have to wait, which is the case since message needs to be fetched from the server.
The two are "incompatible". If we set the prefetch=none on a queue, we should not attempt to use receiveNoWait().
The receiveNoWait() means that the client does not want to wait if message is not immediately available. So this works
well with prefetched messages since they would already be in the client's internal queue. When setting prefetch=none,
the user instructs the client API to fetch individual messages. But then, the nature of receiveNoWait() causes it to return
if it would have to wait, which is the case since message needs to be fetched from the server.
Issue/Introduction
When we set prefetch=none, consumer.receiveNoWait() -Does not seem to work? What is the reason?
Feedback
Yes
No
Powered by
