camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Tam (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-606) JMX enabled as default
Date Thu, 19 Jun 2008 23:23:00 GMT

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

William Tam updated CAMEL-606:
------------------------------

    Attachment: patch.txt

I will update wiki once this patch has been applied.

* By default, Camel mbean objects are registered with a mbean server and performance counters
are enabled. However, RMI connector server is not started by default.
* Mbean server is "found" by mbean server's default domain name as it can be shared among
camel contexts and with other application when it is desirable (as mentioned in CAMEL-613).
* If no mbean server can be found, a new one will be created.  
* As before, it is also possible to use the platform mbean server.
* System properties (found in JmxSystemPropertyKeys.java) and Spring configuration (found
in CamelJMXAgentType.java) support the same set of configuration parameters.
* Instrumentation agent can be disabled by system property or spring configuration.
* Default Instrumentation agent is started and stop by the camel context as a service eliminating
the need for SpringInstrumentationAgent subclass.
* Moved CamelChoiceWithManagementTest from spring to core where it belongs 
* updated RouteBuilderTest, ErrorHandlerTest to account for instrumentation interceptors
* Fixed some of the JMX tests that does not clear and restore system properties properly and
release mbean servers at the end of the test.
* Update AggregatorType to allow it to be wrapped by interceptors.
* add ErrorHandlerWrappingStrategy mechanism as we need to prevent instrumentation interceptor
from being wrapped by ErrorHandlers.
* rename LifecycleStrategy.onContextAdd() to onContextStart() since the lifecycle strategy
is typically created after camel context.  Therefore, we are not really able to invoke the
lifecycle strategy at that time.  It's more meaningful to be notified when camel context is
started instead.
* since the default domain name for the mbean server and the domain name of the registered
mbean object can be differ, we make them into different properties.  
* Add a check in ProcessorType.wrapProcessorInInterceptors() to prevent intercept ref from
changing target processor.  It is a potential cycling problem.  This problem is discovered
by enabling instrumentaton interceptor in StreamCachingInterceptorTest.  We'll probably should
revisit StreamCachingInterceptor.  I'll create a JIRA.
* workaround NPE (CAMEL-620) in ResequencerType to allow createProcesssor to be invoked (so
we can wrap Resequencer by an interceptor).
*  add async support for InstrumentationProcessor
* Fix CAMEL-553 (Firewall-friendly JMX Connector URL) by adding a property for RMI connection
port.


> JMX enabled as default
> ----------------------
>
>                 Key: CAMEL-606
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-606
>             Project: Apache Camel
>          Issue Type: Wish
>          Components: camel-core
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.4.0
>
>         Attachments: patch.txt
>
>
> > Hi
> >
> > Should we consider enabling JMX as default in Camel? It runs on JDK1.5 and thus
its possible.
> Yeah, I think we should.
> > What is the default in ServiceMix? Maybe Camel should align what they do?
> AFAIK ServiceMix and ActiveMQ default it to true. Folk should have to disable it IMHO
as its so useful
> --
> James
> -------

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message