java.lang.ExceptionInInitializerError

This exception has no message.

Solutions on the web8219

  • This exception has no message.
  • via Terracotta by hashcode, 1 year ago
    This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.lang.ExceptionInInitializerError at org.omnifaces.util.Beans.getManager(Beans.java:88) at org.omnifaces.util.Beans.getReference(Beans.java:113) at org.omnifaces.application.OmniApplication.<init>(OmniApplication.java:70) at org.omnifaces.application.OmniApplicationFactory.createOmniApplication(OmniApplicationFactory.java:89) at org.omnifaces.application.OmniApplicationFactory.getApplication(OmniApplicationFactory.java:54) at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:93) at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:142) at com.sun.faces.lifecycle.ClientWindowFactoryImpl.<init>(ClientWindowFactoryImpl.java:62) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at javax.faces.FactoryFinderInstance.getImplGivenPreviousImpl(FactoryFinderInstance.java:405) at javax.faces.FactoryFinderInstance.getImplementationInstance(FactoryFinderInstance.java:251) at javax.faces.FactoryFinderInstance.getFactory(FactoryFinderInstance.java:543) at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:283) at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:328) at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:236) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:439) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4842) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5303) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1407) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1397) 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.IllegalStateException: CDI BeanManager instance is not available in JNDI. at org.omnifaces.config.BeanManager.<init>(BeanManager.java:97) at org.omnifaces.config.BeanManager.<clinit>(BeanManager.java:47) ... 30 more Caused by: java.lang.IllegalStateException: javax.naming.NamingException: Cannot create resource instance at org.omnifaces.util.JNDI.lookup(JNDI.java:95) at org.omnifaces.config.BeanManager.<init>(BeanManager.java:93) ... 31 more Caused by: javax.naming.NamingException: Cannot create resource instance at org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:96) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) at org.apache.naming.NamingContext.lookup(NamingContext.java:841) at org.apache.naming.NamingContext.lookup(NamingContext.java:152) at org.apache.naming.NamingContext.lookup(NamingContext.java:829) at org.apache.naming.NamingContext.lookup(NamingContext.java:152) at org.apache.naming.NamingContext.lookup(NamingContext.java:829) at org.apache.naming.NamingContext.lookup(NamingContext.java:166) at org.apache.naming.SelectorContext.lookup(SelectorContext.java:157) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.omnifaces.util.JNDI.lookup(JNDI.java:90) ... 32 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago