Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-13996

JMS Event listener - add option to define Durable subscriber name

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • rel-4-9-1
    • None
    • Security Level: Users (General product issues)
    • GUI manual test, JUnit test
    • ExportImportTest.testConfigurationImportExport()

    Description

      JMS Event Listener on server has an option to connect to an endpoint as a durable subscriber.

      In this model, the listener identifies to the JMS broker with some name. Currently, this name is not configurable - it is autogenerated in format subscr_<node-id>_<listener-id>.

      For some use cases, it is important to be able to configure this name. One of these use cases is following:

      • JMS topic, all messages from the topic should be consumed exactly once
      • 4-node cluster
      • Listener is configured with single-instance failover - i.e. exactly one instance of listener should be active at all times across the cluster
      • When the node with active listener goes down (e.g. HW or network failure), a different cluster node starts up the listener. But now the durable subscriber name is different because nodeId is different. With a different subscriber name, the JMS messages received are not the ones following the place where the previous listener instance left.

      Acceptance criteria:

      • durable subscriber name can be configured to be always the same regardless of the node where the listener instance runs
      • backwards compatible

      Attachments

        1. image-2018-08-07-16-08-01-757.png
          image-2018-08-07-16-08-01-757.png
          4 kB
        2. image-2018-08-07-16-15-29-232.png
          image-2018-08-07-16-15-29-232.png
          28 kB
        3. image-2018-10-02-15-30-46-632.png
          image-2018-10-02-15-30-46-632.png
          10 kB
        4. JMS.cfg
          0.3 kB
        5. screenshot-1.png
          screenshot-1.png
          6 kB
        6. screenshot-2.png
          screenshot-2.png
          12 kB
        7. screenshot-3.png
          screenshot-3.png
          112 kB

        Issue Links

          Activity

            People

              krivanekm Milan Krivanek
              salamonp Pavel Salamon
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 2 hours
                  2d 2h