[ 
https://issues.apache.org/jira/browse/HADOOP-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HADOOP-14952:
---------------------------------
    Summary: Catalina use of hadoop-client throws ClassNotFoundException for 
jersey   (was: Newest hadoop-client throws ClassNotFoundException)

> Catalina use of hadoop-client throws ClassNotFoundException for jersey 
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-14952
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14952
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0-beta1
>            Reporter: Kamil
>
> I was using org.apache.hadoop:hadoop-client in version 2.7.4 and it worked 
> fine, but recently had problems with CGLIB (was conflicting with Spring).
> I decided to try version 3.0.0-beta1 but server didn't start with exception:
> {code}
> 16-Oct-2017 10:27:12.918 SEVERE [localhost-startStop-1] 
> org.apache.catalina.core.ContainerBase.addChildInternal 
> ContainerBase.addChild: start:
>  org.apache.catalina.LifecycleException: Failed to start component 
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
>         at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:158)
>         at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
>         at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
>         at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
>         at 
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
>         at 
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: 
> com/sun/jersey/api/core/DefaultResourceConfig
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:348)
>         at 
> org.apache.catalina.startup.WebappServiceLoader.loadServices(WebappServiceLoader.java:188)
>         at 
> org.apache.catalina.startup.WebappServiceLoader.load(WebappServiceLoader.java:159)
>         at 
> org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1611)
>         at 
> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1131)
>         at 
> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:771)
>         at 
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:298)
>         at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
>         at 
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5092)
>         at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152)
>         ... 10 more
> Caused by: java.lang.ClassNotFoundException: 
> com.sun.jersey.api.core.DefaultResourceConfig
>         at 
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1299)
>         at 
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1133)
>         ... 21 more
> {code}
> after adding com.sun.jersey:jersey-server:1.9.1 to my dependencies the server 
> started, but I think that it should be already included in your dependencies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to