Documentation for JMS prefetch could use some correction and amplification

Details

Description

(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)

Praveen Murugesan
added a comment - 16/Feb/12 18:39 I'm not quite sure, if there is an option called "capacity" in the address string. I am not able to find one digging into AMQConnectionURL (perhaps something changed?).
I've added a patch to add more information about the maxprefetch option

Praveen, I have applied your patch with some updates: I changed 'number' to 'integer', and removed the section describing the JVM system property and instead cross referenced with the existing documentation for that.

Robbie Gemmell
added a comment - 19/Feb/12 23:02 Praveen, I have applied your patch with some updates: I changed 'number' to 'integer', and removed the section describing the JVM system property and instead cross referenced with the existing documentation for that.

Also meant to say, the change isnt published yet on the site. I cant currently generate all of the docs and dont want to just publish some of it so I will wait until I can. It will certianly be put up before the release itself goes out though (and I'm intending to get auto-publication running at some point, because its annoying haivng to do it manually ).

Robbie Gemmell
added a comment - 19/Feb/12 23:07 Also meant to say, the change isnt published yet on the site. I cant currently generate all of the docs and dont want to just publish some of it so I will wait until I can. It will certianly be put up before the release itself goes out though (and I'm intending to get auto-publication running at some point, because its annoying haivng to do it manually ).