I opened a Proton JIRA a couple weeks ago about corrupted payloads from ActiveMQ for redelivered messages but wasn't sure whether this was something that should be the responsibility of the Proton JMS jar or something that needs fixed in ActiveMQ and was hoping to get some input.
The link to the JIRA is here: https://issues.apache.org/jira/browse/PROTON-624 Basically when you configure ActiveMQ to use transport.transformer=jms and you have a BytesMessage that gets redelivered, its payload is corrupted (or rather ends up being all 0's) because it doesn't get reset when going out through that outbound transformer. This problem does not exist with the default outbound transformer (AMQPNativeOutboundTransformer) because it does a reset as part of the outbound transform process. It looked like the simple fix would be to patch Proton's JMSMappingOutboundTransformer class but I wanted to confirm with the ActiveMQ devs whether or not this is something that should be handled in ActiveMQ when redelivering rather than relying on the Proton layer's outbound transformers to do the BytesMessage reset. Thanks, Jesse
