[ https://issues.apache.org/activemq/browse/CAMEL-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60292#action_60292 ]
Hadrian Zbarcea commented on CAMEL-2854: ---------------------------------------- Michael, if there is a problem, we'll fix it, but it's not clear what you're doing. If you have a route that starts with; {code} from("direct:UserCancelJobRequest").[...] {code} then you will have a consumer for that direct endpoint. So it looks to me that you don't have such a route and hence no such consumer, yet you try to send messages to such an endpoint from another route using something like: {code} from(some-endpoint-probably-jms).[...].to("direct:UserCancelJobRequest")[...]; {code} My guess though is that you are actually using camel embedded in activemq and your activemq upgrade from 5.2.0 to 5.3.2 caused an upgrade of camel from 1.5.0 to 2.2.0. There are slight changes in camel 2.x, including the dsl syntax, that you should take a look at. I am fairly certain that your route syntax is not totally right with camel 2.2.0. I hope this helps. Showing us your route or posting a unit test will allow us understand what's going on and help you better. If you have concerns about posting things that may be proprietary to your organization you could also ask for help on the [#camel irc channel|http://camel.apache.org/irc-room.html]. > No consumers available on "direct://xyz" endpoint > ------------------------------------------------- > > Key: CAMEL-2854 > URL: https://issues.apache.org/activemq/browse/CAMEL-2854 > Project: Apache Camel > Issue Type: Bug > Components: camel-core > Affects Versions: 2.2.0 > Environment: ActiveMQ 5.3.2 / Camel 2.2.0 > Reporter: Michael Chen > Priority: Blocker > > The following warning in log4j log shows up with no predictable reason: > 2010-06-24 14:07:01,090 WARN > [DefaultMessageListenerContainer-7:DirectProducer.java:42] No consumers > available on endpoint: Endpoint[direct://UserCancelJobRequest] to process: > Exchange[JmsMessage: > RunnerBase{locationToRunId='DV02YcABTE43HTRPATEGCBFk0m0', jobrun_id=1234, > requestOrigId='null', secretKey='null', replyToQueueOrTopic='null', > corrolationId='null', requestCreationTime=Thu Jun 24 14:07:01 PDT 2010}] > The endpoint [direct://UserCancelJobRequest] could be a number of different > endpoints in our application and all of them are of "direct:" type. When > this happens, all messages that run through that endpoint will fail, and it > will never recover unless the application is restarted. > Also, if I restart the application and use that route immediately, that > warning will not occur and the request will finish successfully. It seems to > happen to routes that have not been used for a while after startup. > When this happens, I can find the exact Camel endpoint/route/processor in > JConsole, and nothing seems to be wrong. How can a "direct:" endpoint runs > out of consumer? Isn't the thread that product this warning THE thread to > process the message? > We recently upgraded from 5.2 to 5.3.2 and this starts to show up randomly. > It is a show stopper! > --Michael -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.