Hi, Ophir, (Jonathan from EMR here)
Are you using emr-4.1.0 or emr-4.2.0? I just tried this with emr-4.2.0 and
found that http://<my-server>:8890/api/notebook works for me, but http://
<my-server>:8890/api/notebook/2A94M5J1Z fails. For some reason it doesn't
quite fail with the same exception that you're seeing, but it definitely
seems like a similar cause anyway. Here's the exception I get:
WARN [2016-01-13 20:34:52,279] ({qtp508683864-37}
ServletHandler.java[doHandle]:590) - Error for /api/notebook/2A94M5J1Z
java.lang.AbstractMethodError:
javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
at
javax.ws.rs.WebApplicationException.validate(WebApplicationException.java:186)
at javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:88)
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:503)
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:207)
I found that the Zeppelin classpath includes two different jars that
contain the javax/ws/rs/core/Response class:
/usr/lib/zeppelin/lib/javax.ws.rs-api-2.0-m10.jar
and /usr/lib/zeppelin/lib/jersey-core-1.13.jar
What's weird though is that if I remove either of these from the classpath,
the Zeppelin server fails to start up for different reasons. If I
remove /usr/lib/zeppelin/lib/jersey-core-1.13.jar,
I get a ClassNotFoundException for
com.sun.jersey.core.util.FeaturesAndProperties,
and if I remove /usr/lib/zeppelin/lib/javax.ws.rs-api-2.0-m10.jar, I get a
ClassNotFoundException for javax.ws.rs.NotFoundException.
According to a `mvn ... dependency:tree` in the zeppelin-server submodule,
/usr/lib/zeppelin/lib/jersey-core-1.13.jar comes indirectly from
zeppelin-server's direct dependency
on com.sun.jersey:jersey-servlet:jar:1.13:compile, and
/usr/lib/zeppelin/lib/javax.ws.rs-api-2.0-m10.jar
comes from zeppelin-server's direct dependency on
javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile.
Both of these dependencies seem to have been added a long time ago, and
both seem to be used by the websocket API rather than the REST API (at
least based upon the Git commit descriptions where they were added), so
this confuses me even more.
Does anybody from the Zeppelin side have any idea what is going on here?
Thanks,
Jonathan
On Wed, Jan 13, 2016 at 5:34 AM Ophir Cohen <oph...@gmail.com> wrote:
> Hi All,
> We migrated our Zeppelin to use EMR Zeppelin. It's straight forward and we
> were happy with the migration till we found out that something isn't
> working well with the rest API.
>
> Calling to the interpreter API:
> http://<my-server>:8890/api/interpreter
> and this:
> http://<my-server>:8890/api/interpreter/setting
> Returns results as expected.
>
> When trying to access the notebooks:
> http://<my-server>:8890/api/notebook
> Or a specific notebook:
> http://<my-server>:8890/api/notebook/2A94M5J1Z
> It fails with HTTP 500 error.
>
> The error I can see in the logs is NoSuchMethodError (see below) which
> suggests we might have here 'jar-hell' and the wrong (probably old) jar
> loaded instead of the need one - but I can't figure that out.
> Thanks!
>
> The exception:
> WARN [2016-01-13 07:47:11,690] ({qtp716961517-38}
> ServletHandler.java[doHandle]:590) - Error for /api/notebook/2A94M5J1Z
> java.lang.NoSuchMethodError:
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at
> javax.ws.rs.ClientErrorException.<init>(ClientErrorException.java:88)
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:503)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:207)
>
