Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Tue, 19 Jan 2016 16:56:39 +0000 (UTC)
From: "pavan kumar kolamuri (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12932437.1453215061000.149218.1453222599893@Atlassian.JIRA>
In-Reply-To: <JIRA.12932437.1453215061000@Atlassian.JIRA>
References: <JIRA.12932437.1453215061000@Atlassian.JIRA>
 <JIRA.12932437.1453215061741@arcas>
Subject: [jira] [Commented] (FALCON-1758) APIs fail when oozie workflow
 entries are deleted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

pavan kumar kolamuri commented on FALCON-1758:
----------------------------------------------

[~pragya.mittal] Looks like stacktrace copied was not related can you confirm is it correct or not ?

> APIs fail when oozie workflow entries are deleted
> -------------------------------------------------
>
>                 Key: FALCON-1758
>                 URL: https://issues.apache.org/jira/browse/FALCON-1758
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>            Assignee: pavan kumar kolamuri
>             Fix For: 0.9
>
>
> Whenever a process is scheduled in Falcon Native Scheduler and instances are running , later if those workflow entries got deleted , then entity deletion fails with following exception
> {noformat}
> 2016-01-19 14:41:42,280 ERROR - [ActiveMQ Session Task-56:] ~ Error in listener org.apache.falcon.handler.SLAMonitoringHandler (WorkflowJobEndNotificationService:245)
> java.lang.NullPointerException
> 	at org.apache.falcon.service.FeedSLAMonitoringService.makeFeedInstanceAvailable(FeedSLAMonitoringService.java:273)
> 	at org.apache.falcon.handler.SLAMonitoringHandler.updateSLAMonitoring(SLAMonitoringHandler.java:63)
> 	at org.apache.falcon.handler.SLAMonitoringHandler.onSuccess(SLAMonitoringHandler.java:48)
> 	at org.apache.falcon.workflow.WorkflowJobEndNotificationService.notifyWorkflowEnd(WorkflowJobEndNotificationService.java:235)
> 	at org.apache.falcon.workflow.WorkflowJobEndNotificationService.notifySuccess(WorkflowJobEndNotificationService.java:105)
> 	at org.apache.falcon.messaging.JMSMessageConsumer.invokeListener(JMSMessageConsumer.java:218)
> 	at org.apache.falcon.messaging.JMSMessageConsumer.onMessage(JMSMessageConsumer.java:114)
> 	at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1393)
> 	at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
> 	at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
> 	at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> 	at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> 2016-01-19 14:41:42,280 INFO  - [ActiveMQ Session Task-56:] ~ Late date handling not applicable for entityType: PROCESS, entityName: LogMoverTest-agregator-coord16-3c67a0aa operation: GENERATE (LateRerunHandler:231)
> {noformat}
> However if the same is done for entities scheduled with oozie scheduler, entity deletion happens successfully.


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