[ 
https://issues.apache.org/jira/browse/SPARK-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239871#comment-15239871
 ] 

David Wood commented on SPARK-12154:
------------------------------------

Just some experience noted here.  I'm running tomcat 7 with Jersey 2.7 and 
Swagger for jersey2.  My app runs fine until I add the spark-mllib-2.11 
dependency.  After that, tomcat starts, but throws 3 exceptions and won't run 
my app.

MultiException stack 1 of 3
java.lang.NullPointerException
        at 
com.sun.jersey.core.provider.jaxb.AbstractJAXBProvider.setConfiguration(AbstractJAXBProvider.java:109)
...
MultiException stack 2 of 3
java.lang.IllegalStateException: Unable to perform operation: method inject on 
com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App
        at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:449)
...
MultiException stack 3 of 3
java.lang.IllegalStateException: Unable to perform operation: create on 
org.glassfish.jersey.message.internal.MessageBodyFactory
        at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:443)

> Upgrade to Jersey 2
> -------------------
>
>                 Key: SPARK-12154
>                 URL: https://issues.apache.org/jira/browse/SPARK-12154
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Build, Spark Core
>    Affects Versions: 1.5.2
>            Reporter: Matt Cheah
>
> Fairly self-explanatory, Jersey 1 is a bit old and could use an upgrade. 
> Library conflicts for Jersey are difficult to workaround - see discussion on 
> SPARK-11081. It's easier to upgrade Jersey entirely, but we should target 
> Spark 2.0 since this may be a break for users who were using Jersey 1 in 
> their Spark jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to