Mule

JMX domain for MBeans should be configurable.

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: 1.1-rc1
  • Component/s: Modules: Management / JMX
  • Labels:
    None
  • Similar Issues:
    MULE-2273 Integrate JBossTS' JMX mbeans into Mule subdomain
    MULE-582 An endpoint that is used by multiple receivers breaks MBean registration (JMX Agent)
    MULE-2518 MBean's name to be configurable via getter/setter
    MULE-1633 JMX transport for invoking/querying MBeans
    MULE-1892 Detect default WrapperManager MBean for non-Mule processes
    MULE-1349 JMX subsystem broken due to multiple 'Model Started' notifications received
    MULE-2333 Profiler MBeans must be registered under Mule's domain
    MULE-1788 JMX domain property is ignored for JmxAgent
    MULE-134 Improve Jmx support
    MULE-1174 Log4j MBeans are not registered under Mule domain

Description

Since we can deploy any number of mule-spring instances within a single JBoss server, one per SAR, it's important to namespace their management domains.

Perhaps this could be achieved by using the mule-configuration id.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment - 10/Oct/06 10:46 AM

All old Resolved issues transitioned into a Closed state.

Show
Andrew Perepelytsya added a comment - 10/Oct/06 10:46 AM All old Resolved issues transitioned into a Closed state.

People

Vote (0)
Watch (0)

Dates

  • Created:
    17/May/05 04:01 PM
    Updated:
    10/Oct/06 10:46 AM
    Resolved:
    01/Jun/05 04:50 PM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.