-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
The LegacyLDAPSecuritySettingPlugin ldap entries containing $ are incorrectly interpreted with the customized any-word ($) configuration .
Customized configuration
<wildcard-addresses>
<enabled>true</enabled>
<delimiter>.</delimiter>
<single-word>*</single-word>
<any-words>$</any-words>
</wildcard-addresses>
<address-setting match="$"/>
<address-setting match="activemq.management$"/>
<security-setting match="$"/>
Observations in a clustered setup:
If the node with a consumer is restarted, the other node gets a series of following exceptions:
AMQ224037: cluster connection Failed to handle message AMQ222139: Remote queue binding logd7bb33fb-9569-11f0-9c1e-a86daaf37465 has already been bound in the post office. Most likely cause for this is you have a loop in your cluster due to cluster max-hops being too large or you have multiple cluster connections to the same nodes using overlapping addresses
With this, intermittently the messages stop moving from the node with exceptions to the node with the consumers (even with a valid redistribution-delay)
Reproducer:
https://github.com/avi5kdonrh/amq-custom-wilcard
This used to work fine with 7.11 and started causing issues with the release of 7.12
- clones
-
-
- Dev Complete
-
