You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "shashank (Jira)" <ji...@apache.org> on 2026/10/06 09:50:00 UTC
[jira] [Assigned] (CAMEL-25073) camel-management - MBean registration: follow-ups from the deep review
[ https://issues.apache.org/jira/browse/CAMEL-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
shashank reassigned CAMEL-25073:
--------------------------------
Assignee: shashank
> camel-management - MBean registration: follow-ups from the deep review
> ----------------------------------------------------------------------
>
> Key: CAMEL-25073
> URL: https://issues.apache.org/jira/browse/CAMEL-25073
> Project: Camel
> Issue Type: Bug
> Components: camel-management
> Reporter: Claus Ibsen
> Assignee: shashank
> Priority: Minor
>
> Follow-ups found in the review of CAMEL-25065 (https://github.com/apache/camel/pull/26959), not changed there:
> # A CamelContext name (or management name pattern) with , = : " * ? fails to start, as the context key of the object names is not quoted (every query that builds the context key would have to change too).
> # A context-scoped onException is one definition in every route, so its processors share one MBean, which is unregistered when one of the routes is removed.
> # Two endpoints that only differ in a masked secret get the same object name; removing one unregisters the other's MBean.
> # Thread pools created by the same source (such as the aggregate's recover and timeout checkers) get the same object name.
> # Components are registered with mbeansLevel=ContextOnly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)