Camel
  1. Camel
  2. CAMEL-4770

Add startAsync option to JMS consumer endpoint to allow route to be started, but the connection to the remote broker occurs async

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.10.0
    • Component/s: camel-jms
    • Labels:
      None
    • Estimated Complexity:
      Advanced

      Description

      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

      1. AsyncStartListener2.patch
        4 kB
        Michał Warecki
      2. JMXFlag.patch
        5 kB
        Michał Warecki

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Claus Ibsen
            Reporter:
            Claus Ibsen
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development