Bug 472312 - Prefetch information
Summary: Prefetch information
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 1.1
Hardware: All
OS: Linux
high
high
Target Milestone: 1.3
: ---
Assignee: Jonathan Robie
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-19 23:36 UTC by William Henry
Modified: 2013-08-06 00:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description William Henry 2008-11-19 23:36:23 UTC
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:
https://wiki.108.redhat.com/wiki/index.php/AMQP:154,162:Proposal

Also Jonathan had some slides on no-acquire and pre-acquire in the training material. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Jonathan Robie 2009-11-30 14:55:37 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.