Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] Cannot deploy a WAB in OSGi Jetty 9 because of javax.naming.NameNotFoundException; remaining name 'java:comp'

I'm trying to deploy a simple WAB application inside an OSGi container that has installed the Jetty 9.2.10 bundles and the JAX-RS Jersey 2.17 bundles.

All the bundles start correctly and without issues, and when I install my WAB it also installs correctly, but when I start my WAB it sends a JNDI name not found exception, it's really odd because I don't use JNDI whatsoever in my WAB, and the name that the exception is referencing is completely bogus, because it just states the missing JNDI resource name is 'java:comp', which is just the Jetty prefix for JNDI resources, so some Jetty bundle must be trying to setup an empty JNDI resource which causes the problem.

2015-05-15 23:48:29.968:WARN:oejw.WebAppContext:FelixDispatchQueue: Failed startup of context o.e.j.w.WebAppContext@5718e0e{/wab,file:/private/var/folders/3h/w04868ln4j30dwqdscvy8wnw0000gn/T/jetty-0.0.0.0-8080-wab-sample-1.0.0.war-_wab-any-3819588013061278932.dir/webapp/,null}{file:/Users/****/NetbeansProjects/*****/target/bundle/wab-sample-1.0.0.war}
javax.naming.NameNotFoundException; remaining name 'java:comp'

I posted this issue in stackoverflow where I have the full exception and my jetty.xml configuration file.

Thanks for the help!

http://stackoverflow.com/questions/30272184/cannot-deploy-a-wab-in-osgi-jetty-9-because-of-javax-naming-namenotfoundexceptio





Back to the top