You can try to set RedeliveryDelay attribute in your destination configuration file to be something greater than zero.
thank you very much, instance are now recreated with RedeliveryDelay greater than 0.
But is it a normal feature?
Sorry to dig this old thread out, but I have the same issue reported with JBoss 5.1.0. Changing the RedeliveryDelay to > 0 fixed it for me too.
To answer your question: according to the jms 1.1 spec (3.10. "Changing the Value of a Received Message"), this is not expected behavior:
"If the consumer modifies a received message, and the message is subsequently redelivered, the
redelivered message must be the original, unmodified message (except for headers and properties
modified by the JMS provider as a result of the redelivery, such as the JMSRedelivered header and
the JMSXDeliveryCount property)."
@JBM-developers: will this be fixed in a 1.x release in the near future? Or maybe it's enough to set RedeliveryDelay to 1 per default?!