It is possible for this to happen normally. For example, when using the failover transport and temporarily losing connection to the broker, the client might not realize that the consumer removal was already processed on the broker due to the lost connection, and therefore may resend it on reconnecting.
This error message can be safely ignored unless other issues of concern arise, such as lost messages. -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-5-10-0-Cannot-remove-a-consumer-that-had-not-been-registered-tp4689351p4689414.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
