qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell" <gemme...@dcs.gla.ac.uk>
Subject RE: [jira] Commented: (QPID-1469) AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user[MESSAGE NOT SCANNED]
Date Mon, 01 Dec 2008 10:46:18 GMT
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.

-----Original Message-----
From: aidan.skinner@gmail.com [mailto:aidan.skinner@gmail.com] On Behalf Of
Aidan Skinner
Sent: 01 December 2008 10:19
To: qpid-dev@incubator.apache.org
Subject: Re: [jira] Commented: (QPID-1469)
AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid
user[MESSAGE NOT SCANNED]

On Mon, Dec 1, 2008 at 1:24 AM, Robbie Gemmell <gemmellr@dcs.gla.ac.uk>
wrote:

> One issue with making it on by default is that everyone will need to
download the jmxremote_optional.jar and add it to the classpath to start the
broker, even for testing...which I believe is the reason it was turned off
by default in the first place, I recall seeing it in a commit message when
scouring the backlog previously.

We should probably integrate MX4J (http://mx4j.sourceforge.net/)
instead, this is what Tomcat, Geronimo etc use. The OpenDMK stuff
seems to still be propreitary, although it's a little hard to tell if
that's intentional or not.

- 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


Mime
View raw message