title: Camel - DirectConsumerNotAvailableException No consumers available on endpoint
body: <p>I have been searching for this issue on Google as well as here on Stackoverflow.  I've seen several others report this same exception, and although I understand what the suggested solution is, I am not 100% if I am witnessing the exact same problem if you will.</p>
  
  <p>Of course, here's the exception:</p>
  
  <p>I have a Camel project with two routes.  Here's a simplification:</p>
  
  <pre><code>&lt;route&gt;
    &lt;from uri="jetty://http://0.0.0.0:8181/listener"/&gt;
    &lt;to uri="direct:ProcessMessage"/&gt;
  &lt;/route&gt;
  
  &lt;route&gt;
    &lt;from uri="direct:ProcessMessage"/&gt;
    ...
  &lt;/route&gt;
  </code></pre>
  
  <p>So this code snippet works fine most of the time.  However, I was attempting to test the scalability of code.  At what point does system start to fail?</p>
  
  <p>When sending the box 100 messages per second on the listener endpoint above (using Jetty), I start seeing this in the logs:</p>
  
  <pre><code>org.apache.camel.component.direct.DirectConsumerNotAvailableException: No consumers available on endpoint: Endpoint[direct://ProcessMessage]
  </code></pre>
  
  <p>The solutions I have seen state this occurs because the order of the routes (i.e. how they're being initialized).  If that is true in this situation, why does this only happen under heavier load and not all the time?</p>