Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2031
@franz1981 So I think that you could avoid subclassing the
ActiveMQBytesMessage if you built the properties yourself instead of calling
setObjectProperty in setAMQMsgObjectProperties in the converter as that is
where the trigger point is for allocating the bytes stream (see
initializeWriting and its uses in ActiveMQBytesMessage). In a manner similar
to how the converter puts the body into the message using setContent you could
create and marshal the properties and store them using setMarshalledProperties
in the OpenWire base Message class. The properties are marshalled using the
utility class MarshallingSupport#marshalPrimitiveMap so it is possible to roll
your own and then bypass that bit of the ActiveMQMessage's normal handling.
---
