Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-226

Tests for subscribing/listening to multiple active-mq topics

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.3
    • 0.5
    • common, messaging, rerun

    Description

      Post-processing step of parent workflow uses Falcon system JMS topic to send messages, which are used for retrying failed instances and handling late rerun.

      Before migration, IVORY.ENTITY.TOPIC is used for sending the messages, which is hard-coded in post-processing classes, post migration new processes send messages to FALCON.ENTITY.TOPIC.

      However, the subscriber to listen to this topic is configurable in startup.properties
      *.entity.topic=FALCON.ENTITY.TOPIC

      So, after migration, admin needs to configure the topic to listen to both old and new ENTITY.TOPIC, since activemq supports multiple topic subscription so a comma separated topic list should be configured.

      *.entity.topic=FALCON.ENTITY.TOPIC,IVORY.ENTITY.TOPIC

      More test-cases needs to be added to FalconTopicProducer and FalconSubscriberService.

      Attachments

        1. FALCON-226.patch
          16 kB
          Shaik Idris Ali
        2. FALCON-226-v1.patch
          16 kB
          Shaik Idris Ali

        Activity

          People

            shaik.idris Shaik Idris Ali
            shaik.idris Shaik Idris Ali
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified