It is a broker bug, which is being exposed by a change in the client from years ago. The client is not marking the messages durable, the broker is, but only internally as the message coming out is again not marked durable.
Specifically, this line: https://github.com/apache/activemq/blob/activemq-5.15.9/activemq-amqp/src/main/java/org/apache/activemq/transport/amqp/message/AMQPRawInboundTransformer.java#L47 looks likely to be interacting with this one: https://github.com/apache/activemq/blob/activemq-5.15.9/activemq-amqp/src/main/java/org/apache/activemq/transport/amqp/message/InboundTransformer.java#L92 to make the broker treat a non-durable message as persistent, as it marks it persistent when it isnt, and when the message has a header but defaulted (which is false) durable field, it doesnt mark the message non-persistent when it should. It looks like you could perhaps try the brokers 'jms' transformer as workaround vs the 'native' default, as it doesnt run that first line. See: http://activemq.apache.org/amqp.html Robbie On Fri, 26 Apr 2019 at 10:59, [email protected] <[email protected]> wrote: > > Thanks Robbie for quick response. > > To me it seemed to be Qpid JMS library issue because I could reproduce this > issue with any version(ActiveMQ 5.14.4 onwards) of broker with Qpid JMS > v0.20.0 onwards where as with old version of Qpid JMS (i.e. v0.11.1 and > prior) and with any version of broker (ActiveMQ 5.14.4 onwards) it works > fine. > > Not sure if you got a chance to look into the sample Utility I shared. > > Regards, > Hardik > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
