Hi, you can specify createConnector=false on a management context and in that way you can only access JMX from the local machine (no ports will be open). Jconsole will see this process nicely, but you'll have to use Sun JDK to access JMX API exposed in this way.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Dec 1, 2009 at 6:18 PM, Fred Moore <fred.moor...@gmail.com> wrote: > Hi folks, > I have a completely embedded broker instance running in the same JVM as my > JMS applications, all applications use a VM transport connector so the > "TCP/IP footprint" (i.e. used ports) of this system is currently zero. > > Now my additional requirement is to be able to remove some [unused] broker > queues programmatically via a new service application running in the same > JVM as the broker. > > Is there a way of performing this simple operation without having my broker > listening on a TCP/IP port (and consequently introducing the need for > locking down admin access with security credentials management etc)? > > For instance this wiki > http://activemq.apache.org/how-do-i-delete-a-destination.html points to > JMX > which -- AFAIK -- requires listening on TCP/IP to start with. > > I'm I missing something obvious here? > Thanks in advance. > Cheers, > F. >
