Skip to content

default threadNamePattern #661

@ivan-ra

Description

@ivan-ra

Camel 4 routes have different thread names in standalone and osgi mode. This is the same route and endpoint on karaf and standalone:

Image

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# ");

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions