How to close client connections from the server side?

[jendo]

I was hoping to be able to close a client connection using HornetQServerControl.closeConnectionsForAddress but it requires an IP address and I don't know what address to use and I don't even see a way to find out what addresses are connected. I thought perhaps I could use ClientSession.addMetaData to associate certain information with the clients in order to know which one I want to disconnect, but I don't see a way to see this meta data on the server side. So then I thought I could just use HornetQServerControl.destroyQueue but that throws an exception when there is still a consumer on the queue. Is there any way to override this?

[jendo]

Of course after I post this, I see HornetQServerControl.listAddresses which gives me all IP Addresses, but it still doesnt help me filter which one is the one I want to use.

[clebert.suconic]

What version?

Latest version has some metadata on Consumers and Sessions that helps you find them based on clientIDs (assuming you are using client-ids, or any other metadata)

[jendo]

I'm sorry, I should have specified. I am using 2.2.5.Final. Also, I am just using core libraries, nothing JMS.

[clebert.suconic]

There's a method on the Core-Session called addMetaData();

This is a temporary hack, but maybe it would work:

You could add two attributes to your client metadatas:

session.addMetaData("jms-session","1");

sesison.addMetaData("jms-client-id","something-that-identify-your-client");

on JMSServerControl, you would be able to use listConnectionsAsJSON();

You will then have the address exposed, to something more specific to your clients.

We may add some method on Core to print the connections and their entire meta-data. (you could maybe add a JIRA?)

[jendo]

Thank you for the response. I have tried adding meta data on the session as you suggested but JMSServerControl.listConnectionsAsJSON is not returning any information.

[jendo]

I see the addMetaData being discussed here but I don't see any way to retrieve that meta data using the HornetQServerControl. Is this information accessed some other way? If not, what is the purpose of adding meta data?

[clebert.suconic]

There's a JIRA for adding support on non-jms objects (to list it through CoreControl).

At this point it's only available through JMS Server Control.

I don't know why it didn't work for you. You could probably find out easily with some easy debug.

[jendo]

Ok, I got it working. What I was missing was

session.addMetaData("jms-session","1");

I assume the value has to be unique among all the clients, correct?

Thanks again for your help!