jamesnetherton opened a new pull request, #9314: URL: https://github.com/apache/camel-quarkus/pull/9314
Fixes #9313. The management extension `CamelContextCustomizer` explicitly called `context.setManagementName(context.getName())`. Because `JmxManagementLifecycleStrategy.onContextStarting` only consults the `ManagementNameStrategy` when the management name is `null`, this meant `camel.main.jmxManagementNamePattern` was never applied. This removes the call. Camel assigns the management name itself on CamelContext startup, so with the default pattern (`#name#`) the resolved name is unchanged. The `setManagementNameStrategy` call, which is the actual fix for #7522, is retained. Changes: - Remove `setManagementName` from `CamelManagementRecorder` - Add `ManagementNamePatternTest` / `ManagementNamePatternIT`, which run with `camel.main.jmxManagementNamePattern=custom-#name#` and assert the management name and MBean `ObjectName` context key are resolved from the pattern. The test fails without the fix - Add a 4.0.0 migration guide note, since applications that already set the option will see their MBean `ObjectName` values change Testing: JVM mode tests pass for the `management`, `micrometer`, `jolokia`, `debug` and `controlbus-statistics` integration tests. Native mode was not run locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
