title: Spring Integration
body: <p>Our application has been designed using Spring Integration Framework. Complete message action flow starts with listening to Queue's for which JMS message driven adapters has been used after which channel based i.e. queue endpoints have been defined and each endpoint is processed by Service-Activators.</p>
  
  <p>We are currently into performance phase, we are spawning 200 message request. Initially we observed that messages were not executing in parallel, after doing some reading figured out that by adding concurrent-consumer and max-concurrent-consumer property to JMS message driven listener adapter will help to enable multi-threading mode. Indeed this helped but still somewhere in between the process I still see Single Thread effect. Is this due to way the endpoint has been defined? What is the advantage of adding Queue capacity to each endpoint? Do you think by adding queue-capacity to each Channel endpoint definition will again help to run in mutli-threading mode.</p>
  
  <p>The design snapshot as requested:</p>
  
  <p><img src="https://i.stack.imgur.com/ETnfE.jpg" alt="action flow"></p>