There were no changes in Stomp part on how to deal with this header, so it must be something else changed to cause this. It would be the best if you could create a test case of what you expect so we can nail it down.
There's no way to define redelivery policy using CONNECT header at the moment. Any contribution is more than welcomed. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Mon, Aug 15, 2011 at 9:50 AM, Aleksandar Ivanisevic < aleksan...@ivanisevic.de> wrote: > > since 5.4.2 at least (and in 5.5.0) I'm no longer getting redelivered: > header in redelivered messages. I'm using STOMP if that matters. Is > this a feature or a "feature"? I was using this header to do some > basic redelivery management on the client and even if i redo it at the > broker level it would still be useful to know if a message is a > redelivery or not. > > How does one configure redelivery policy with STOMP, just send the > headers from http://activemq.apache.org/redelivery-policy.html at > CONNECT? Is it possible to configure redelivery policy using xml on > the broker? If so, are there any examples somewhere? > > >
