Details
-
Type:
Bug
-
Status:
Pending 3rd-Party
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.3
-
Fix Version/s: None
-
Component/s: Modules: Management / JMX
-
Labels:None
-
Similar Issues:
MULE-2333Profiler MBeans must be registered under Mule's domainMULE-1892Detect default WrapperManager MBean for non-Mule processesMULE-253JMX domain for MBeans should be configurable.
MULE-2273 Integrate JBossTS' JMX mbeans into Mule subdomainMULE-2518MBean's name to be configurable via getter/setterMULE-4583Configurable registration of the Log4jAgent in DefaultJmxSupportAgentMULE-1633JMX transport for invoking/querying MBeans
MULE-3976 Improve log4j agent to handle log4j zeroconfMULE-282JMXAgent is not fully disposed ofMULE-5756Fantasy domain pointed when creating a mule module using archetype
Issue Links
| Related | |||
|---|---|---|---|
|
|||
Well, it might not make it to the 1.3.1 release due to the hardcoded JMX domain in log4j (sigh...).
There's a patch available http://issues.apache.org/bugzilla/show_bug.cgi?id=40251 dated Aug-14-2006, but is hasn't been applied yet.