users@jersey.java.net

[Jersey] Re: javax.naming.NoInitialContextException and other Exceptions

From: Paul Sandoz <Paul.Sandoz_at_oracle.com>
Date: Thu, 6 Jan 2011 14:34:48 +0100

Hi,

Those messages are harmless. You don't need to worry about them, since
you are not using EE 6 features.

The messages are logged at Level.CONFIG (at least for Jersey 1.4 and i
think it is the case for earlier versions as well). So usually for
default log level setting they should not been seen. What is your log
level set to?

Paul.

On Jan 6, 2011, at 1:03 PM, Martin Spuetz wrote:

> Hello,
>
> i got Jersey running with Jetty. Works like a charm! But I still get
> Exceptions in my log.
>
>> 2011-01-06 12:45:36,276 INFO [main]
>> c.s.j.s.i.e.EJBComponentProviderFactoryInitilizer:86 - The EJB
>> interceptor binding API is not available. JAX-RS EJB support is
>> disabled.
>> javax.naming.NoInitialContextException: Need to specify class name
>> in environment or system property, or as an applet parameter, or in
>> an application resource file: java.naming.factory.initial
>> at
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
>> 645) ~[na:1.6.0_17]
>> at
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:
>> 288) ~[na:1.6.0_17]
>> at
>> javax
>> .naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:
>> 325) ~[na:1.6.0_17]
>> at javax.naming.InitialContext.lookup(InitialContext.java:
>> 392) ~[na:1.6.0_17]
>
>> 2011-01-06 12:45:36,279 INFO [main]
>> c.s.j.s.i.j.JCDIComponentProviderFactoryInitializer:70 - The JCDI
>> BeanManager is not available. JAX-RS JCDI support is disabled.
>> javax.naming.NoInitialContextException: Need to specify class name
>> in environment or system property, or as an applet parameter, or in
>> an application resource file: java.naming.factory.initial
>> at
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
>> 645) ~[na:1.6.0_17]
>> at
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:
>> 288) ~[na:1.6.0_17]
>> at
>> javax
>> .naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:
>> 325) ~[na:1.6.0_17]
>> at javax.naming.InitialContext.lookup(InitialContext.java:
>> 392) ~[na:1.6.0_17]
>
>> 2011-01-06 12:45:36,673 INFO [main]
>> c.s.j.s.i.m.ManagedBeanComponentProviderFactoryInitilizer:81 - The
>> managed beans injection manager API is not available. JAX-RS
>> managed beans support is disabled.
>> javax.naming.NoInitialContextException: Need to specify class name
>> in environment or system property, or as an applet parameter, or in
>> an application resource file: java.naming.factory.initial
>> at
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
>> 645) ~[na:1.6.0_17]
>> at
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:
>> 288) ~[na:1.6.0_17]
>> at
>> javax
>> .naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:
>> 325) ~[na:1.6.0_17]
>> at javax.naming.InitialContext.lookup(InitialContext.java:
>> 392) ~[na:1.6.0_17]
>
> My web.xml:
>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
>> ">
>> <display-name>dnsadmin</display-name>
>> <servlet>
>> <servlet-name>ServletAdaptor</servlet-name>
>> <servlet-
>> class>com.sun.jersey.spi.container.servlet.ServletContainer</
>> servlet-class>
>> <init-param>
>> <param-name>com.sun.jersey.config.property.packages</
>> param-name>
>> <param-value>webapps.rest</param-value>
>> </init-param>
>> <load-on-startup>1</load-on-startup>
>> </servlet>
>> <servlet-mapping>
>> <servlet-name>ServletAdaptor</servlet-name>
>> <url-pattern>/*</url-pattern>
>> </servlet-mapping>
>> <session-config>
>> <session-timeout>30</session-timeout>
>> </session-config>
>> <welcome-file-list>
>> <welcome-file>index.html</welcome-file>
>> </welcome-file-list>
>> </web-app>
>
> I have only one simple rest service but it is working. Do I have to
> worry about the exceptions?
>
> Thanks,
> Martin