On Nov 22, 2017 10:43 PM, "dfco21" <aelba...@hotmail.com> wrote:
Exact. The consumer which had the 2 messages is the one which is supposed to get the 5 messages. It's a consumer-broker created by another cloud service supposed to consume the 5 messages sent. OK, so the consumer you're looking at is another broker, not an "end" consumer? I don't feel like you've really given us a very good description of what you're actually doing, which makes it hard to know what questions to ask or suggestions to make. It looks like the 2nd consumer with the 3 messages is created by the producer. But 5 messages have been produced and no broker has been configured on the producer side. On what are you basing the guess that it's created by the producer? Does it appear when the producer starts and disappear when the producer stops? Does the connection come from the producer's IP address? Maybe it's a networked broker as you mentioned but how can I confirm. You're going to want to investigate further via a JMX viewer such as JConsole. The web console is great for getting status of the broker, but when you need to investigate something (as you do now), the more-detailed information available through JMX is really what you want. The MBeans exposed via JMX will let you see which IP and port that connection comes from, which will let you tie it to the process that owns it. As I said no broker has been configured to get created by the producer and 3 of the 5 messages are not consumed by the correct broker. So there's only supposed to be these two brokers networked together? No other brokers? Who's supposed to be consuming these messages (from the other broker, by implication of what you wrote above)? Is that consumer connected to the right broker? Explanations I see: * the 2nd broker is created by the producer but why 3 messages are consumed not 5? I'm not following this. If five messages are published to a queue with two consumers, why would you expect either one to get all five? * the 1st broker has not enough time to consume the message and a 2nd default broker consumes it Unless you've enabled slow consumer strategies, this wouldn't be the case. Clearly you have two consumers and you expect only one, which fully explains the behavior you're seeing, so use JMX to figure out what the other consumer is and go from there. They are only hypothesis, I am not sure how to confirm and fix the issue. Below the producer properties: <http://activemq.2283324.n4.nabble.com/file/t378791/Picture2.png> Thanks for your time and help. -AEB -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
