You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Prabhjyot Singh (JIRA)" <ji...@apache.org> on 2017/09/21 12:00:20 UTC

[jira] [Created] (AMBARI-22021) Livy not working with the default configuration

Prabhjyot Singh created AMBARI-22021:
----------------------------------------

             Summary: Livy not working with the default configuration
                 Key: AMBARI-22021
                 URL: https://issues.apache.org/jira/browse/AMBARI-22021
             Project: Ambari
          Issue Type: Bug
            Reporter: Prabhjyot Singh


This started failing with ZEPPELIN-2909, which introduces `"className": "org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with following exception;


{code:java}
java.lang.NullPointerException
	at org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
	at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
	at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
	at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
	at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	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)
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)