[
https://issues.apache.org/jira/browse/ARTEMIS-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311007#comment-16311007
]
ASF GitHub Bot commented on ARTEMIS-1577:
-----------------------------------------
Github user shailendra14k commented on the issue:
https://github.com/apache/activemq-artemis/pull/1744
@michaelandrepearce, Most the places what I observed is prefixes are
removed like:-
artemis-core-client:- QueueAbstractPacket class while getting the address
prefix are removed.
https://github.com/apache/activemq-artemis/blob/master/artemis-core-client/src/main/java/org/apache/activemq/artemis/core/protocol/core/impl/wireformat/QueueAbstractPacket.java#L49-L60
When getting the ProducerCredits [1], the prefix is removed before getting
the store from PagingManager, due to which the address setting policies are
ignored as it will always get a wrong store.
https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/ServerSessionImpl.java#L1412-L1424
I was not able to find a way other then updating the CoreMessage method
getAddressSimpleString which is used at most places for getting the queue name.
> 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)
