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 2015/03/05 18:43:38 UTC

[jira] [Resolved] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

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

Timothy Bish resolved AMQ-5560.
-------------------------------
    Resolution: Fixed

Fixed on master, searched the filters for a matching DescribedType with the correct descriptor along with some other code cleanup.  This patch does not yet account for a case where there could be multiple instances of the same filter type in the filters list.  

> AMQP: use type descriptors to inspect AMQP filter types rather than the map keys
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-5560
>                 URL: https://issues.apache.org/jira/browse/AMQ-5560
>             Project: ActiveMQ
>          Issue Type: Sub-task
>          Components: AMQP
>    Affects Versions: 5.10.0, 5.10.1, 5.11.0
>            Reporter: Robbie Gemmell
>            Assignee: Timothy Bish
>             Fix For: 5.12.0
>
>
> The broker is currently looking up AMQP filters using named keys of the filter map. This approach is fragile, since difference clients may name equivalent filters differently, as the names are not intended to identify particular types. The broker should instead inspect the descriptor values when trying to identify the particular type of a filter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)