[
https://issues.apache.org/jira/browse/CAMEL-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227354#comment-13227354
]
Michał Warecki commented on CAMEL-4770:
---------------------------------------
Great solution. At the start of Camel excess threads could cause problems with
memory. I think I will take into account the problem of large number of threads
in the pool while designing an alerts mechanism
(http://camel.465427.n5.nabble.com/DISCUSS-Camel-Alerts-td5497221.html).
I think we should open a new ticket for the new JMX flags because, due to
unified management solution in the Camel, it will cover all consumers. One
solution would be to add new interface (extending org.apache.camel.Service)
with method isRunning() or isAlive() and add the same method to
org.apache.camel.management.mbean.MenagedService and
org.apache.camel.api.management.mbean.ManagedServiceMBean. Implementation would
be like in org.apache.camel.CamelContext.ManagedService#getState. I will try to
implement this solution when I find some free time.
> 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
