Flume
  1. Flume
  2. FLUME-2313

Start the source even if the JMS queue/topic is not available

    Details

    • Type: Bug Bug
    • Status: Patch Available
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: v1.4.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Release Note:
      Hide
      adding the ability to start the jms source even if the jms server is down.
      Each time the source is called, the source will try to reconnect if there is no connexion.
      Show
      adding the ability to start the jms source even if the jms server is down. Each time the source is called, the source will try to reconnect if there is no connexion.

      Description

      Currently, if the jms server is not available, the Flume jms source do not start and never will.
      We would like the source to be able to start even if the server is not available and connect lately.
      I'll try to provide a patch sooner.

        Issue Links

          Activity

          Hugo Lassiège created issue -
          Hugo Lassiège made changes -
          Field Original Value New Value
          Link This issue is cloned as FLUME-2311 [ FLUME-2311 ]
          Hugo Lassiège made changes -
          Release Note Use of JNDI lookup to find destination. The default mode still use "Create destination identifier" mode. Use destinationLocator=JNDI to enable this feature
          Description Here https://issues.apache.org/jira/browse/FLUME-924?focusedCommentId=13890651&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13890651

          [~hlassiege] says:

          I'm currently using this jms source to connect on Weblogic message bus. I'm wondering why the JMSMessageConsumer use createQueue and createTopic instead of lookup to find the destinations (line 83 to 90).
          It seems that "createQueue" or "createTopic" are not the recommended way because it is not portable (I saw that warning in Weblogic documentation even if I can't justify this assertion).
          The documentation recommends to use a JNDI lookup (http://docs.oracle.com/cd/E23943_01/web.1111/e13727/lookup.htm#BABDFCIC).
          Is there any reason to use createQueue instead of lookup ?
          Currently, if the jms server is not available, the Flume jms source do not start and never will.
          We would like the source to be able to start even if the server is not available and connect lately.
          I'll try to provide a patch sooner.
          Hide
          Hugo Lassiège added a comment - - edited

          This patch add the ability to start the jms source even if the jms server is down.
          Each time the source is called, the source will try to reconnect if there is no connexion.

          Be carreful, this patch applied after the patch submitted for FLUME-2311.

          Show
          Hugo Lassiège added a comment - - edited This patch add the ability to start the jms source even if the jms server is down. Each time the source is called, the source will try to reconnect if there is no connexion. Be carreful, this patch applied after the patch submitted for FLUME-2311 .
          Hugo Lassiège made changes -
          Hugo Lassiège made changes -
          Link This issue is cloned as FLUME-2311 [ FLUME-2311 ]
          Hugo Lassiège made changes -
          Link This issue relates to FLUME-2311 [ FLUME-2311 ]
          Hide
          Hugo Lassiège added a comment -

          The patch in FLUME-2311 have to be applied prior to this patch.

          Show
          Hugo Lassiège added a comment - The patch in FLUME-2311 have to be applied prior to this patch.
          Hugo Lassiège made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Release Note adding the ability to start the jms source even if the jms server is down.
          Each time the source is called, the source will try to reconnect if there is no connexion.

            People

            • Assignee:
              Unassigned
              Reporter:
              Hugo Lassiège
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development