that is a sort of firewall, dynamic white/black list, type feature and we don't have anything like that atm. maybe reverting to OS level firewall rules can keep that client away once you know its ip.
This has come up before in the context of the abortslowconsumer policy, where an aborted client will keep coming back and some sort of temp blacklist would be required to reject it early. The best impl would probably route back to iptables rules - as the most efficient way to block consumers. That sort of feature could be built via a broker filter but there is already a bunch of work done (connection creation etc) at that stage so it is not ideal. So maybe iptables is your best bet. On 12 March 2014 09:58, khandelwalanuj <[email protected]> wrote: > Hi, > > I am using ActiveMQ v5.8. When a consumer try to connect to the broker with > the client id which is already used previously. broker throws > "InvalidClientID" exception. > Client is using spring DMLC and it will keep on retrying indefinitely to > connect again even after receiving the exceptions. > > I don't want such clients to try to connect to the broker again and again. > And i don;'t have access to the client configuration. So Is there a way to > stop(kill) such clients from broker side ? > > Thanks, > Anuj > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-consumer-not-getting-removed-tp4678812.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
