I agree, redelivery of request messages means you're not acking them correctly, and a change in behavior due to changing your redelivery policy further proves the point. You say you're doing that, but I don't see it in the code you posted. Am I missing something?
Tim On Jan 28, 2016 1:43 PM, "Bjand" <bj...@danskebank.dk> wrote: > Some extra info: I managed to consistently get 1:1 in my request/response > code. I did this by changing the redeliverypolicy.maximumRedeliveries to 0. > I don't like this solution, but suggests that problem is acknowledgement of > messages. I have previously acknowledge in the code by calling the > msg.acknowledge method. This do not solve the problem. > > Another observation is that the problem does not exist when the > request/response messages are called on the same connection. It is does > show > when the response code is running in a windows service, and request is > called from a client on a different machine. > > Any ideas what the hopefully simple problem is? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Receiving-multiple-duplicate-messages-Beginner-question-tp4706474p4706607.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
