[ 
https://issues.apache.org/jira/browse/CXF-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aki Yoshida updated CXF-4170:
-----------------------------

    Description: 
We introduced a simpler mechanism for configuring the instrumentation manager 
with CXF-3992, namely using the bus properties instead of directly configuring 
the InstrumentationManagerImpl bean. Unfortunately, this change introduced an 
issue in setting the instrumentation bean properties configured using the old 
style of directly configuring the instrumentation manager bean.

In particular, when setting each property of the InstrumentationManagerImpl 
bean, those properties that are set before the bus property is set are not 
correctly set with the desired values. For example, if the bus property is set 
at the beginning, the rest of the properties appearing below this line are 
correctly set. However, if the bus property is set not at the beginning, those 
properties appearing above that line are not set correctly and overwritten by 
the default values. 

Note that this problem does not occur when the properties are set using the bus 
properties

In any case, this problem needs to be fixed.

  was:
We introduced a simpler mechanism for configuring the instrumentation manager 
bean with CXF-3992, namely using the bus properties instead of directly 
configuring the bean. Unfortunately, this change introduced an issue in reading 
the instrumentation bean properties configured using the old style of directly 
configuring the instrumentation manager bean. 

In particular, when setting each property of the InstrumentationManagerImpl 
bean, those properties that are set before the bus property is set are not 
correctly set. In other words, if the bus property is set at the beginning, the 
rest of the properties are correctly read. However, if the bus property is set 
not at the beginning, those properties appearing above are overwritten by the 
default values.

Note that this problem does not occur when the properties are set using the bus 
properties

In any case, this problem needs to be fixed.

        Summary: JMX InstrumentationManager's configuration properties may not 
be set correctly in standalone mode after upgrading to 2.5.2  (was: JMX 
InstrumentationManager's configuration properties may not be read correctly in 
standalone mode after 2.5.2)
    
> JMX InstrumentationManager's configuration properties may not be set 
> correctly in standalone mode after upgrading to 2.5.2
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4170
>                 URL: https://issues.apache.org/jira/browse/CXF-4170
>             Project: CXF
>          Issue Type: Bug
>          Components: Management
>    Affects Versions: 2.5.2
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.5.3, 2.6
>
>
> We introduced a simpler mechanism for configuring the instrumentation manager 
> with CXF-3992, namely using the bus properties instead of directly 
> configuring the InstrumentationManagerImpl bean. Unfortunately, this change 
> introduced an issue in setting the instrumentation bean properties configured 
> using the old style of directly configuring the instrumentation manager bean.
> In particular, when setting each property of the InstrumentationManagerImpl 
> bean, those properties that are set before the bus property is set are not 
> correctly set with the desired values. For example, if the bus property is 
> set at the beginning, the rest of the properties appearing below this line 
> are correctly set. However, if the bus property is set not at the beginning, 
> those properties appearing above that line are not set correctly and 
> overwritten by the default values. 
> Note that this problem does not occur when the properties are set using the 
> bus properties
> In any case, this problem needs to be fixed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to