camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicky Sandhu <nickysan...@hotmail.com>
Subject Monitoring and management of Camel
Date Thu, 07 Jun 2007 20:18:55 GMT

Looking ahead to when camel would be in deployment some features are needed
for management, monitoring
Runtime Management/Monitoring
1.) A registry of contexts and the routes in them
2.) JMX interface to this registry with ability to add/remove routes and
start/stop contexts
3.) Ability to deploy a new route to a running context (once context is
started can routes be added?)
4.) Ability to support restarts ie add/removing route to a running context
should be persistent
5.) Support for notification via JMX or something else when changes happen
to a context
6.) Support for notification when errors happen during processing of a route
message. (reminds me of cross-cutting requirement across some/all routes,
AOP based??)

There are two options available to maintaining multiple camel contexts in a
running JVM
1.) WAR deployments to a J2EE container
2.) Bundle deployments to OSGi container

Both these options provide the ability to have multiple camel contexts
running without interferring with each other (class loading issues and such)

Is there anything on the road maps to address these needs?

-- 
View this message in context: http://www.nabble.com/Monitoring-and-management-of-Camel-tf3886171s22882.html#a11015466
Sent from the Camel - Users mailing list archive at Nabble.com.


Mime
View raw message