[
https://issues.apache.org/jira/browse/ARTEMIS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000470#comment-17000470
]
ASF subversion and git services commented on ARTEMIS-2581:
----------------------------------------------------------
Commit 13278cc45f47cd14f7d29678d3d41036442ee20b in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=13278cc ]
ARTEMIS-2581 Duplicate Detection on AMQP should be configurable
There is an optimization in AMQP, that properties are only parsed over demand.
It happens that after ARTEMIS-2294 (commit
2dd06716989820eeecad7f39faabfbb8f025f7f1),
every send would request for the property on the message, resulting the
properties to always be parsed upon send.
Even when there's no use of application properties.
> Make Duplicate Detection Optional on AMQP, default=true
> -------------------------------------------------------
>
> Key: ARTEMIS-2581
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2581
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.10.1
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is an optimization in AMQP, that will allow to parse application
> properties only when needed.
> It happens that after ARTEMIS-2294 (commit
> 2dd06716989820eeecad7f39faabfbb8f025f7f1) when we look for the application
> property for the duplicate ID, we parse all the application properties.
> There's no way to turn off that even if the user is not using duplicate
> detection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
