Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1757
@franz1981 re the checkProperties change, its not thread safe. And i'd
rather not put synchronised block in.
Found this on running larger test suite. On checking duplicate it seems as
efficient as it can be as in its just an object wrapping around the existing
bytebuf, with new index's effectively, so i reverted that change (i get same
perf result btw on load testing).
I think real solution is to get those core properties like routingtype to
the core message level, as such then they will be more efficient and
lazyproperties can be truely honoured server side and not decoded at all.
---
