[
https://issues.apache.org/jira/browse/CAMEL-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226838#comment-13226838
]
Claus Ibsen commented on CAMEL-4770:
------------------------------------
Thanks Michael.
I decided to use a shared cached thread pool on JmsComponent, this is to ensure
each startup task gets a dedicated thread to run, as they can potentially take
a long time and/or block. Also the cached thread pool will shrink when the task
is no longer in use. And its better to have a shared thread pool, than a thread
pool per consumer, that could add a lot of thread pools for people with many
JMS routes.
> Add startAsync option to JMS consumer endpoint to allow route to be started,
> but the connection to the remote broker occurs async
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4770
> URL: https://issues.apache.org/jira/browse/CAMEL-4770
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.10.0
>
> Attachments: AsyncStartListener2.patch
>
>
> This allows people to add routes which consumes from JMS destinations, by
> which the consumer should start async in a separate thread, this ensures
> Camel will continue starting the route, and continue the code. Then the asyns
> thread starts the JmsConsumer in the background. This is needed in case the
> remote connection to the JMS broker does not work. But you want to signal the
> route is started anyway, as the JMS consumer most likely support failover and
> retry, so the connection may come online later.
> We may need to add some way to store a flag, so you from JMX can monitor if
> the JMS consumer is live or not.
> See nabble
> http://camel.465427.n5.nabble.com/Adding-JMS-route-may-block-if-remote-is-down-using-failover-connection-tp5037014p5037014.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
