Is this still a problem? I would trace into the convertAndSend() call - you want to get down to the ActiveMQMessageProducer's send() call and verify that it has NON_PERSISTENT mode set.
If NON_PERSISTENT mode is set on the ActiveMQMessageProducer's send() call, and the messages are getting to the broker with PERSISTENT mode, that sounds like a bug. On the other hand, if they are PERSISTENT in the same send() call, somewhere between the JMS template and the actual producer, the setting is getting lost. -- View this message in context: http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457p4680984.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
