You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/09/23 20:59:26 UTC

[jira] [Resolved] (AMQ-3242) Change prefetch size limit for topics from 32766 to 32767

     [ https://issues.apache.org/jira/browse/AMQ-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-3242.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0

Fix applied in trunk, apache site updated to reflect the change.

> Change prefetch size limit for topics from 32766 to 32767
> ---------------------------------------------------------
>
>                 Key: AMQ-3242
>                 URL: https://issues.apache.org/jira/browse/AMQ-3242
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Robert Liguori
>            Priority: Trivial
>             Fix For: 5.6.0
>
>
> The default prefetch size limit for topics is noted as 32766; http://activemq.apache.org/performance-tuning.html
> The FUSE source documentation (http://fusesource.com/docs/broker/5.4/tuning/index.html) states, "Default prefetch limit is 32766. The default limit of 32766 is the largest value of a short and is the maximum possible value of the prefetch limit.".
> The largest value for a short actually is 32767 (http://java.sun.com/docs/books/jls/second_edition/html/typesValues.doc.html).
> This is really a trivial issue, but should the default prefetch limit for topics be changed from 32766 to 32767 to reflect the actual ceiling?
> And of course, I would recommend changing the automatic setting to 32767, when the maximum has been exceeded.  The following warning shows the applied default of 32766:
> 16:22:40 WARN  maximum prefetch limit has been reset from 50000 to 32766

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira