You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Peeyush Bishnoi (JIRA)" <ji...@apache.org> on 2015/10/30 11:54:28 UTC

[jira] [Commented] (FALCON-1564) Provide an option for users to disable system post-processing JMS notification

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

Peeyush Bishnoi commented on FALCON-1564:
-----------------------------------------

[~pallavi.rao] Thanks for providing the patch. I have applied and tested the patch, it works as expected. 

In Falcon application log, I am seeing the following exception. Instead of exception stack trace, can we just put the log statement.

{code:java}
2015-10-30 10:18:27,794 DEBUG - [ActiveMQ Session Task-3:] ~ Error while retrieving JMS connection info (OozieWorkflowEngine:607)
E1601 : E1601: Cannot retrieve JMS connection info [JMSTopicService is not initialized. JMS notificationmay not be enabled]
        at org.apache.oozie.client.OozieClient.handleError(OozieClient.java:612)
        at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:982)
        at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:969)
        at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:560)

{code}

> Provide an option for users to disable system post-processing JMS notification
> ------------------------------------------------------------------------------
>
>                 Key: FALCON-1564
>                 URL: https://issues.apache.org/jira/browse/FALCON-1564
>             Project: Falcon
>          Issue Type: Bug
>          Components: rerun
>    Affects Versions: 0.8
>            Reporter: Peeyush Bishnoi
>            Assignee: Pallavi Rao
>            Priority: Blocker
>             Fix For: trunk, 0.8
>
>         Attachments: FALCON-1564.patch
>
>
> On running the Falcon process entity with retry option and with defined number of attempts, I have found that not a single retry is happening upon instance failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)