ivan-ra opened a new issue, #661: URL: https://github.com/apache/camel-karaf/issues/661
Camel 4 routes have different thread names in standalone and osgi mode. This is the same route and endpoint on karaf and standalone: <img width="1134" height="566" alt="Image" src="https://github.com/user-attachments/assets/a8e647d5-6e12-4582-8660-efc18865640c" /> It would be more convenient if the naming policy was uniform. It is quite difficult to find the required threads on karaf because all have almost the same names "Camel (camel-#) thread ... " On previous versions (at least camel2) thread name policies was uniform. As workaround for now route configuration requires this code (or similar blueprint code): ``` camelContext.getCamelContextExtension().setName(this.getClass().getSimpleName()); // set default pattern camelContext.getExecutorServiceManager().setThreadNamePattern("Camel (#camelId#) thread ##counter# - #name# "); ``` -- 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]
