After clean build still receiving the same error.


> On Jan 6, 2015, at 3:59 PM, Sean Owen <so...@cloudera.com> wrote:
> 
> FWIW I do not see any such error, after a "mvn -DskipTests clean package" and 
> "./bin/spark-shell" from master. Maybe double-check you have done a full 
> clean build.
> 
>> On Tue, Jan 6, 2015 at 9:09 PM, Ganon Pierce <ganon.pie...@me.com> wrote:
>> I’m attempting to build from the latest commit on git and receive the 
>> following error upon attempting to access the application web ui:
>> 
>> HTTP ERROR: 500
>> 
>> Problem accessing /jobs/. Reason:
>> 
>>     Server Error
>> Powered by Jetty://
>> 
>> My driver also prints this error:
>> 
>> java.lang.UnsupportedOperationException: empty.max
>>      at scala.collection.TraversableOnce$class.max(TraversableOnce.scala:216)
>>      at scala.collection.AbstractTraversable.max(Traversable.scala:105)
>>      at 
>> org.apache.spark.ui.jobs.AllJobsPage.org$apache$spark$ui$jobs$AllJobsPage$$makeRow$1(AllJobsPage.scala:46)
>>      at 
>> org.apache.spark.ui.jobs.AllJobsPage$$anonfun$jobsTable$1.apply(AllJobsPage.scala:91)
>>      at 
>> org.apache.spark.ui.jobs.AllJobsPage$$anonfun$jobsTable$1.apply(AllJobsPage.scala:91)
>>      at 
>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>>      at 
>> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>>      at scala.collection.immutable.List.foreach(List.scala:318)
>>      at scala.collection.TraversableLike$class.map(TraversableLike.scala:244)
>>      at scala.collection.AbstractTraversable.map(Traversable.scala:105)
>>      at org.apache.spark.ui.jobs.AllJobsPage.jobsTable(AllJobsPage.scala:91)
>>      at org.apache.spark.ui.jobs.AllJobsPage.render(AllJobsPage.scala:106)
>>      at org.apache.spark.ui.WebUI$$anonfun$attachPage$1.apply(WebUI.scala:68)
>>      at org.apache.spark.ui.WebUI$$anonfun$attachPage$1.apply(WebUI.scala:68)
>>      at org.apache.spark.ui.JettyUtils$$anon$1.doGet(JettyUtils.scala:68)
>>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>      at 
>> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
>>      at 
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
>>      at 
>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
>>      at 
>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
>>      at 
>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
>>      at 
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>>      at 
>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
>>      at 
>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>>      at org.eclipse.jetty.server.Server.handle(Server.java:370)
>>      at 
>> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
>>      at 
>> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
>>      at 
>> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
>>      at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
>>      at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>>      at 
>> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>>      at 
>> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)
>>      at 
>> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
>>      at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>>      at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>>      at java.lang.Thread.run(Thread.java:745)
>> 
>> 
>> Has the ui been disabled intentionally for development purposes, have I not 
>> set something up correctly, or is this a bug?
> 

Reply via email to