Mule Manager ID is not set when using Mule+Spring configuration

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.3.2
  • Fix Version/s: 1.4.2
  • Component/s: Core: Configuration
  • Labels:
    None
  • User impact:
    High
  • Similar Issues:
    None

Description

I am using the mule-spring mixed DTD configuration and I'm seeing the following anomalies:

1. During the eager creation of the beans, the Manager gets started even if I have set the magic system prop to true (or was it false?)

2. For some reason, the manager ID is not set when using the mule+spring config (same file works fine in ordinary mule config). This causes the JMX agent to register the beans under a generated ID which is not very usable.

3. I have the impression that some other props are not set as well, although I cannot put my finger on which ones exactly.

My workaround is to set manually the manager ID before configuration and to pre-register the descriptors which I used to add manually after the config. Still if there is an easy workaround for #1, please let me know.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MULE-2142 Server ID is automatically generated in spite of that "id" attribue is set in mule-configuration

  • Critical - Crashes, loss of data, severe memory leak.
  • 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
Andrew Perepelytsya added a comment -

Dimitar,

Just FYI, AutowireUMOManagerFactoryBean supports the managerId property (available in 1.3.3), maybe it can help.

Show
Andrew Perepelytsya added a comment - Dimitar, Just FYI, AutowireUMOManagerFactoryBean supports the managerId property (available in 1.3.3), maybe it can help.
Hide
Permalink
Dimitar Dimitrov added a comment -

Setting the AutowireUMOManagerFactoryBean manually helps, but this prevents me from using the mule-configuration tag which is more readable and easy to set up.

The real fix would be to patch mule-to-spring.xsl, although I would agree that it's low priority,

Show
Dimitar Dimitrov added a comment - Setting the AutowireUMOManagerFactoryBean manually helps, but this prevents me from using the mule-configuration tag which is more readable and easy to set up. The real fix would be to patch mule-to-spring.xsl, although I would agree that it's low priority,
Hide
Permalink
Andrew Perepelytsya added a comment -

Changing priority to minor, as Mule 2.x will most probably don't have this problem by definition. Time permitting, address in 1.4.

Show
Andrew Perepelytsya added a comment - Changing priority to minor, as Mule 2.x will most probably don't have this problem by definition. Time permitting, address in 1.4.
Hide
Permalink
Andrew Perepelytsya added a comment -

Descoping the 1.4.1, unset Fix Version for some issues.

Show
Andrew Perepelytsya added a comment - Descoping the 1.4.1, unset Fix Version for some issues.
Hide
Permalink
Andrew Perepelytsya added a comment -

r7842

Show
Andrew Perepelytsya added a comment - r7842
Hide
Permalink
Dirk Olmes added a comment -

r7849

Show
Dirk Olmes added a comment - r7849

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: