Is it possible this is an issue with ActiveMQ 5.4.1 despite an older version of NMS working fine?
Gary found an issue with the latest cut which is highly related. He mentions it here: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-4-2-td3058930.html#a3060530 -- View this message in context: http://activemq.2283324.n4.nabble.com/Apache-NMS-ActiveMQ-v1-4-1-and-Durable-Subscription-message-loss-tp3058202p3060536.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
