camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-8435) direct endpoint not available
Date Wed, 04 Mar 2015 14:14:04 GMT

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

Claus Ibsen updated CAMEL-8435:
-------------------------------
    Priority: Major  (was: Critical)

> 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
>
> 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)

Mime
View raw message