Thread name when using ConcurrencyInterceptor

[moores]

I'm seeing that the thread name when using @Concurrency, when logged from within the @MessageEndpoint's @Handler, sometimes is set to the endpoint name + <integer>, while other times it's set to "message bus=<integer>".

Is that a bug?

[Mark Fisher]

The default task executor that is created when using @Concurrency has a CallerRunsPolicy (for throttling input tasks). Therefore, when there are no non-busy threads in the pool, the calling thread (message-bus) invokes the handler directly.