activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4234) Broker destination policy prefetch value is ignored by stomp consumers
Date Thu, 20 Dec 2012 16:15:14 GMT

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

Timothy Bish commented on AMQ-4234:
-----------------------------------

Need to be careful with a fix of two things that I was seeing while trying to fix that other
issue.  You have to find a way to not send the receipt before you really know if the subscribe
worked, and you have to ensure that if it did work that the receipt goes ahead of any dispatched
messages to the client.  Lots of fun racing events in there. 
                
> 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
>            Priority: Minor
>              Labels: default, prefetch, stomp
>
> 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

Mime
View raw message