Shaik Idris Ali created FALCON-226:
--------------------------------------

             Summary: Ivory to Falcon migration stopped Retry and Late Rerun 
service 
                 Key: FALCON-226
                 URL: https://issues.apache.org/jira/browse/FALCON-226
             Project: Falcon
          Issue Type: Bug
          Components: common, messaging, rerun
    Affects Versions: 0.3
            Reporter: Shaik Idris Ali
            Assignee: Shaik Idris Ali


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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to