You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/03/29 02:04:15 UTC

[jira] [Commented] (OOZIE-1765) JMS Notifications for Workflows not always on the correct topic

    [ https://issues.apache.org/jira/browse/OOZIE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951658#comment-13951658 ] 

Hadoop QA commented on OOZIE-1765:
----------------------------------

Testing JIRA OOZIE-1765

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 1 line(s) longer than 132 characters
.    {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1408
.    Tests failed: 1
.    Tests errors: 1

.    The patch failed the following testcases:

.      testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1141/

> 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)