[
https://issues.apache.org/jira/browse/OOZIE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1765:
---------------------------------
Attachment: OOZIE-1765.patch
The problem was in {{JMSTopicService#getTopic(AppType appType, String user,
String jobId, String parentJobId)}} where it had:
{code:java}
topicName = topicMap.get(JobType.WORKFLOW);
{code}
That should have been:
{code:java}
topicName = topicMap.get(JobType.WORKFLOW.value);
{code}
While I was at it, I also added handling bundles to that method and updated
some issues I found in the JMS documentation.
> JMS Notifications for Workflows not always on the correct topic
> ---------------------------------------------------------------
>
> Key: OOZIE-1765
> URL: https://issues.apache.org/jira/browse/OOZIE-1765
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk, 4.0.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-1765.patch
>
>
> If you configure your JMS topics as follows
> {code:xml}
> <property>
> <name>oozie.service.JMSTopicService.topic.name</name>
> <value>
> default=${username},
> WORKFLOW=flows
> </value>
> </property>
> {code}
> you would expect all WORKFLOW_JOB and WORKFLOW_ACTION messages to be on the
> "flow" topic and everything else on the "$\{username}" topic.
> However, that is not the case: everything ends up on the "$\{username}" topic.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
