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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.