[jira] [Commented] (ARTEMIS-1577) Address-settings policies aren't being applied when using an older version of JMS client

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ARTEMIS-1577:
-----------------------------------------

Github user michaelandrepearce commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1744
  
    @shailendra14k if you step through the code and as i highlighted the 
ActiveMQPacketHandler is setting this when the session is made and the client 
version is pre-addressing changes.
    
    see code extract:
    ```
    if (connection.getChannelVersion() < PacketImpl.ADDRESSING_CHANGE_VERSION) {
                routingTypeMap = new HashMap<>();
                routingTypeMap.put(PacketImpl.OLD_QUEUE_PREFIX, 
RoutingType.ANYCAST);
                routingTypeMap.put(PacketImpl.OLD_TOPIC_PREFIX, 
RoutingType.MULTICAST);
             }
    ```


> Address-settings policies aren't being applied when using an older version of 
> JMS client
> ----------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1577
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1577
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Shailendra Kumar singh
>         Attachments: broker.xml
>
>
> Address-settings policies aren't being applied when using an older version of 
> JMS client.
> Example:-
> #broker.xml
> {code:java}
> <address-setting match="exampleQueue">
>                 <address-full-policy>FAIL</address-full-policy>
>                 <max-size-bytes>10</max-size-bytes>
>  </address-setting>
> {code}
> When using JMS client(artemis-jms-client) version 1.5.5, Address-settings 
> policies are not applied.
> When using latest client version, it works as expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)