[
https://issues.apache.org/jira/browse/ARTEMIS-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-5915:
------------------------------------
Description:
If {{id-cache-size}} is set to {{0}} on clustered brokers then bridged messages
will not be routed in the target queue and, therefore, these messages cannot be
receive by the client.
This behavior occurs because when processing a bridged message,
{{checkBridgeDuplicateID}} returns
{{DuplicateCheckResult.DuplicateNotStartedTX}}, meaning the message is
considered a duplicate and is not routed to the queue.
It is caused by an incorrect return value when calling {{atomicVerify}} for the
{{NoOpDuplicateIDCache}} cache implementation.
> Bridge messages are not routed to the queue if id-cache-size=0 on the broker
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-5915
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5915
> Project: Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.33.0, 2.51.0
> Reporter: Dmitriy Nozdrya
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.53.0
>
>
> If {{id-cache-size}} is set to {{0}} on clustered brokers then bridged
> messages will not be routed in the target queue and, therefore, these
> messages cannot be receive by the client.
> This behavior occurs because when processing a bridged message,
> {{checkBridgeDuplicateID}} returns
> {{DuplicateCheckResult.DuplicateNotStartedTX}}, meaning the message is
> considered a duplicate and is not routed to the queue.
> It is caused by an incorrect return value when calling {{atomicVerify}} for
> the {{NoOpDuplicateIDCache}} cache implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
