cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (Created) (JIRA)" <>
Subject [jira] [Created] (CXF-3992) Making JMX instrumentation manager configurable using some bus properties
Date Wed, 21 Dec 2011 17:13:32 GMT
Making JMX instrumentation manager configurable using some bus properties

                 Key: CXF-3992
             Project: CXF
          Issue Type: Improvement
          Components: Management
    Affects Versions: 2.5.1
            Reporter: Aki Yoshida
            Assignee: Aki Yoshida
             Fix For: 2.5.2

In some cases, for example, on an OSGi container having the JMX mbean server service running,
with CXF 2.5.0 and up, there is no need in explicitly configuring the instrumentation manager
bean. In other cases, the instrumentation manager bean may need to be explicitly configured.
Previously, this meant that an instance of the InstrumentationManagerImpl bean must be configured.
And in this case, there was some issue in the consistent association between the bus and its
configured instrumentation manager instance, as initially another instrumentation manager
instance is initially assigned to the bus.

In order to solve this problem and at the same time to simplify the configuration, this patch
introduces a mechanism to directly configure the instrumentation bean using some specific
bus properties.

Here is a sample:
<cxf:bus bus="mybus">
    <entry key="bus.jmx.enabled" value="true"/>
    <entry key="bus.jmx.threaded" value="false"/>     
    <entry key="bus.jmx.daemon" value="false"/>
    <entry key="bus.jmx.JMXServiceURL" value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi"

Property bus.jmx._prop_ corresponds to property _prop_ of the InstrumentationManager bean.


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message