Based on your description I'd say it's the same issue. A fix was committed to the code-base on November 27 so it's not in any release yet (2.4.0 was released on November 7). You can try building from master and testing if you like otherwise I guess you'll need to wait until 2.5.0 is released.
Justin On Fri, Jan 12, 2018 at 1:51 AM, Archibald <arch...@gmx.net> wrote: > The issue occurs only, if the original message is being sent via AMQP (the > receiver itself is a JMS-Consumer). If I use a JMS Producer everything > works > as expected. > > Br, Archibald > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
