You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Aidan Skinner <ai...@apache.org> on 2008/12/01 12:03:52 UTC
JMX remoting (was Re: [jira] Commented: (QPID-1469) AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user[MESSAGE NOT SCANNED])
On Mon, Dec 1, 2008 at 10:46 AM, Robbie Gemmell <ge...@dcs.gla.ac.uk> wrote:
> Could do, although the issue there is that MX4J doesnt implement the JMXMP
> connector and instead have its own connectors based on soap, hessian, or
> burlap which all require Jetty or such like to communicate via http, so that
> means adding that too on broker and console sides.
I think that's a better solution than saying "oh, hey, go download
this other random thing if you want authentication". That's just weak.
- Aidan
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
"Have we anything resembling a plan?" "Mm-hm. Ride till we find
them... and kill them all." - The 13th Warrior
Re: JMX remoting (was Re: [jira] Commented: (QPID-1469)
AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid
user[MESSAGE NOT SCANNED])[MESSAGE NOT SCANNED]
Posted by Robbie Gemmell <ge...@dcs.gla.ac.uk>.
Well it does sound a little naff when put like that :P
On Mon, 2008-12-01 at 11:03 +0000, Aidan Skinner wrote:
> On Mon, Dec 1, 2008 at 10:46 AM, Robbie Gemmell <ge...@dcs.gla.ac.uk> wrote:
>
> > Could do, although the issue there is that MX4J doesnt implement the JMXMP
> > connector and instead have its own connectors based on soap, hessian, or
> > burlap which all require Jetty or such like to communicate via http, so that
> > means adding that too on broker and console sides.
>
> I think that's a better solution than saying "oh, hey, go download
> this other random thing if you want authentication". That's just weak.
>
> - Aidan