Shreya Bhat created AMBARI-20321: ------------------------------------ Summary: Spark livy server stops after starting with address already in use Key: AMBARI-20321 URL: https://issues.apache.org/jira/browse/AMBARI-20321 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Shreya Bhat Fix For: 2.5.0
STR : 1. Restart all services of a host one by one 2. Restart livy server. Start completes successfully 3. Wait for 2 minutes Livy server will stop on its own. The stack trace is here : {code} Exception in thread "main" java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:433) at sun.nio.ch.Net.bind(Net.java:425) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321) at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.server.Server.doStart(Server.java:366) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at com.cloudera.livy.server.WebServer.start(WebServer.scala:93) at com.cloudera.livy.server.LivyServer.start(LivyServer.scala:222) at com.cloudera.livy.server.LivyServer$.main(LivyServer.scala:302) at com.cloudera.livy.server.LivyServer.main(LivyServer.scala) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)