You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/09 12:45:05 UTC

[jira] [Resolved] (CAMEL-8435) direct endpoint not available

     [ https://issues.apache.org/jira/browse/CAMEL-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-8435.
--------------------------------
    Resolution: Not A Problem
      Assignee: Claus Ibsen

> direct endpoint not available
> -----------------------------
>
>                 Key: CAMEL-8435
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8435
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.12.3
>            Reporter: Frédéric Pirson
>            Assignee: Claus Ibsen
>
> When a direct route is accessed before it is started (for example when an activemq route is started and use this direct route and there is 1 waiting message), it indicates that there is No consumers available for endpoint for the current message and all the next messages.
> <route>
>    <errohandler ../> <!-- To deadletter queue--> 
>    <from uri="activemq:testQueue">
>     <to uri="direct:test">
> </route>
> <route>
>    <from uri="direct:test">
>     <to uri="log:...">
> </route>
> stop the application, add a message in the testQueue, set a break point in DefaultCamelContext method doStartOrResumeRoutes. Ensure that the activemq route is started and the message is consumed, the message will go to the deadletter queue because no consumer available. That is correct. but when the direct roure is started and a new message is sent, it still go in the deadletter queue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)