[
https://issues.apache.org/jira/browse/CAMEL-13515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858449#comment-16858449
]
Claus Ibsen commented on CAMEL-13515:
-------------------------------------
Okay found a better way, however to make it more consistent then we both create
and start the producer on the first request. This ensure any kind of error
related to the producer will be lazy; which is a feature Camel users has asked
about in the past.
> Allow producer to lazy start until first message
> ------------------------------------------------
>
> Key: CAMEL-13515
> URL: https://issues.apache.org/jira/browse/CAMEL-13515
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> We could add option to DefaultProducer so any producer allows to defer its
> startup (doStart) to when the first message is being processed. The danger is
> that the startup logic has to be thread-safe and if there are concurrent
> messages then they would need to hold back until the startup is done. This is
> a trade-off that the user would need to accept if enabled.
> But this can make it easier to let Camel startup routes even if some remote
> server is not available when a producer startup as part of route startup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
