That would certainly produce the described behaviour. I've checked very carefully though and I'm 100% certain that I don't have another consumer.
I've discovered a few more things though. I only have two machines involved in this transaction but it seems to only be triggered when I"m using a particular two machines, which suggests to me that the network layout has something to do with. (I have to stress here the the network connection really does work though since I can send messages one way and I'm sure I receive the data back) Out of curiosity I tries starting the comsumer on the machine which I knew would fail, and a short time later starting an identical consumer on a different machine (which doesn't exhibit this problem) and discovered that the second consumer received the message, but only after the first consumers receive() call had timed out and returned null. It's almost like the first consumer is receiving the message but not acknowledging it properly, so after it fails, the broker sends the message to someone else. Any ideas on what could trigger this kind of behaviour? Maybe you have another consumer that consumes that message? Cheers -- Dejan Bosanac -- View this message in context: http://www.nabble.com/Messages-being-consumed-but-not-delivered-to-the-application-tp21845959p21862411.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
