Re: Web UI Error

2017-03-15 Thread Suresh V
It looks like AWS does not support the Oozie web UI anymore. They are recommending to use Hue... -Suresh. On Tue, Mar 14, 2017 at 5:18 AM, Andras Piros wrote: > OK, Suresh, thanks for your input. > > When deploying not to Amazon EMR but to a local Tomcat 6.0.45, do you > encounter the same pro

Re: Web UI Error

2017-03-14 Thread Andras Piros
OK, Suresh, thanks for your input. When deploying not to Amazon EMR but to a local Tomcat 6.0.45, do you encounter the same problem? Actually it seems to me that some Jetty classpaths might be *lurking in

Re: Web UI Error

2017-03-13 Thread Suresh V
Hello Andras, I can reproduce it by just typing the http://:11000 on the browser. This is an AWS EMR 5.0.3 with Oozie version 4.2.0. We created 3 EMR clusters recently of this version, and all three have this problem. I'm about to take this to AWS but wanted to check here if anyone has encountered

Re: Web UI Error

2017-03-12 Thread Andras Piros
Hi Suresh, can you please provide following details: - what are the exact and minimal steps to reproduce, aka what does that exactly mean "when accessing the Oozie web client"? - what is the Oozie version you're trying? Or did you build that from master? - when trying w/ Tomcat 6.0

Web UI Error

2017-03-11 Thread Suresh V
Hello all, We are seeing below error in the browser when accessing the Oozie web client. This is out of the box from an AWS EMR cluster. Any pointers? HTTP Status 500 - java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IP