Dynamically created components are not registered in JMX

Details

  • User impact:
    Medium
  • Effort points:
    2
  • Similar Issues:
    None

Description

If you create a new component (service, receiver, dispatcher, etc.) at runtime it is not exposed in JMX.

The JMX agent should listen to the Model notifications and do the right thing.
Same goes for disposing.

Issue Links

is blocked by

Improvement - An improvement or enhancement to an existing feature or task. MULE-4725 Implement RegistryNotifications

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-3522 Non-working server notifications in JmxAgent

  • To be reviewed - The priority for new issues filed by users
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment -

Good catch, thanks for feeding back

Show
Ross Mason added a comment - Good catch, thanks for feeding back
Hide
Permalink
Daniel Feist added a comment -

Lets look into this one. If it's quick/easy low fix then lets put it in a maintennace release else move it back to 2.x.

Show
Daniel Feist added a comment - Lets look into this one. If it's quick/easy low fix then lets put it in a maintennace release else move it back to 2.x.
Hide
Permalink
Andrew Perepelytsya added a comment -

This could be fixed within the scope of registry notification work.

Show
Andrew Perepelytsya added a comment - This could be fixed within the scope of registry notification work.

People

  • Assignee:
    Andrew Perepelytsya
    Reporter:
    Dimitar Dimitrov
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: