[
https://issues.apache.org/jira/browse/QPID-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Murugesan updated QPID-3679:
------------------------------------
Attachment: prefetch_doc.patch
A small doc update to fix the issue pointed out by Gordon.
> Documentation for JMS prefetch could use some correction and amplification
> --------------------------------------------------------------------------
>
> Key: QPID-3679
> URL: https://issues.apache.org/jira/browse/QPID-3679
> Project: Qpid
> Issue Type: Bug
> Components: Documentation, Java Client
> Affects Versions: 0.12
> Reporter: Gordon Sim
> Attachments: prefetch_doc.patch
>
>
> (1) the documentation states that maxprefetch controls the 'maximum number of
> pre-fetched messages per destination'. However this is not strictly correct,
> it is the prefetch per *consumer* (if you had multiple consumers on the same
> destination they would each have that amount of prefetch).
> (2) there is no mention of the capacity option in the address (which
> admittedly is only supported by the JMS client ta this point)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
