Only one thread is used from consumerExecutor in AsyncBaseLifeCycle.

Solution Verified - Updated -

Issue

In AsyncBaseLifeCycle only one thread does all the work from consumerExecutor even thought it has thread pool. This is highly inefficient and defeats the purpose of having Thread Pool.

Environment

  • Fuse ESB Enterprise 7.1 (servicemix-common JBI component)
  • JBI

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content