[
https://issues.apache.org/jira/browse/OOZIE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954879#comment-13954879
]
Robert Kanter commented on OOZIE-1765:
--------------------------------------
Line longer than 132 characters is a twiki thing. Test failures are unrelated.
> 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)
