[
https://issues.apache.org/jira/browse/CAMEL-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124347#comment-18124347
]
Claus Ibsen commented on CAMEL-25073:
-------------------------------------
Merged for 4.23.0: https://github.com/apache/camel/pull/27461,
https://github.com/apache/camel/pull/27462,
https://github.com/apache/camel/pull/27463 (item 1),
https://github.com/apache/camel/pull/27465 (item 4). Still open:
https://github.com/apache/camel/pull/27464 (item 2), which has an unresolved
review conversation, so the issue stays open.
_Claude Code on behalf of davsclaus_
> 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
> Fix For: 4.23.0
>
>
> 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)
