Red Hat Bugzilla – Bug 472312
Last modified: 2013-08-05 20:53:11 EDT
Description of problem:
There doesn't seem to be a lot of descriptions anywhere on how to use prefetch.
pre-acquire is default .. i.e. it assumes that the consumer is going to take ownership of message and once acknowledged it can be removed from the queue.
no-acquire allows you to fetch messages without acquiring them. This is useful for both subscribing to messages with taking responsibility for processing (stock feed) or for browsing messages on a queue.
I found this very useful:
Also Jonathan had some slides on no-acquire and pre-acquire in the training material.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
In the User's Guide, the Sessions chapter has a section called "Message acquisition and acceptance", which covers this.
The C++ API documentation for Session has a series of examples for "Accepting, Acquiring, Rejecting, or Releasing Messages". The Python API documentation is sparse in general, and does not include this. For both languages, the new high level APIs need to be documented in general.
Java uses the Java JMS API.