[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-4234) Broker destination policy prefetch value is ignored by stomp consumers
From:       "Gary Tully (JIRA)" <jira () apache ! org>
Date:       2012-12-21 14:45:44
Message-ID: JIRA.12624838.1356019559732.42960.1356101144508 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQ-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538104#comment-13538104 \
] 

Gary Tully commented on AMQ-4234:
---------------------------------

@Tim, fix was to run prefetch values propagated through consumer control commands via \
the policyentry. Failover (setting prefetch to 0 and back) suffered the same problem. \

> Broker destination policy prefetch value is ignored by stomp consumers
> ----------------------------------------------------------------------
> 
> Key: AMQ-4234
> URL: https://issues.apache.org/jira/browse/AMQ-4234
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.7.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Labels: default, prefetch, stomp
> Fix For: 5.8.0
> 
> 
> Introduced in https://issues.apache.org/jira/browse/AMQ-3895
> we use a prefetch value of 0 to ensure no dispatch till we get can receipt the sub. \
> But we may need to find a better way. Such that the prefetch values can be default \
> on the way in and get applied by the broker. Also, our default values should mirror \
> the broker defaults based on destination and sub type, currently the all default to \
> 1000.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]