Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-1758

APIs fail when oozie workflow entries are deleted

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.9
    • 0.9
    • scheduler
    • None

    Description

      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

      2016-01-19 14:41:42,261 INFO  - [ActiveMQ Session Task-56:] ~ Logging in pragya (CurrentUser:65)
      2016-01-19 14:41:42,261 INFO  - [ActiveMQ Session Task-56:] ~ Creating Oozie client object for http://192.168.138.236:11000/oozie/ (OozieClientFactory:50)
      2016-01-19 14:41:42,267 DEBUG - [ActiveMQ Session Task-56:] ~ Error while retrieving JMS connection info (OozieWorkflowEngine:613)
      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:542)
              at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:869)
              at org.apache.oozie.client.OozieClient$JMSInfo.call(OozieClient.java:856)
              at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:514)
              at org.apache.oozie.client.OozieClient.getJMSConnectionInfo(OozieClient.java:912)
              at org.apache.falcon.workflow.engine.OozieWorkflowEngine.isNotificationEnabled(OozieWorkflowEngine.java:604)
              at org.apache.falcon.workflow.WorkflowJobEndNotificationService.notifyWorkflowEnd(WorkflowJobEndNotificationService.java:214)
              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,267 INFO  - [ActiveMQ Session Task-56:] ~ Creating Oozie client object for http://192.168.138.236:11000/oozie/ (OozieClientFactory:50)
      
      

      However if the same is done for entities scheduled with oozie scheduler, entity deletion happens successfully.

      Attachments

        1. FALCON-1758.patch
          9 kB
          pavan kumar kolamuri
        2. FALCON-1758-v1.patch
          11 kB
          Pallavi Rao

        Issue Links

          Activity

            People

              pavan kumar pavan kumar kolamuri
              pragya.mittal Pragya Mittal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: