0 Replies Latest reply on Mar 18, 2009 10:53 PM by Neil C

    No application context active on WebLogic at Startup

    Neil C Novice

      I know there are a lot of reasons for this error, but I am finding it immediately upon deployment before even any application logs get written:



      java.lang.IllegalStateException: No application context active
              at org.jboss.seam.Component.forName(Component.java:1799)
              at org.jboss.seam.Component.getInstance(Component.java:1849)
              at org.jboss.seam.Component.getInstance(Component.java:1844)
              at org.jboss.seam.Component.getInstance(Component.java:1821)
              at org.jboss.seam.Component.getInstance(Component.java:1816)
              at org.jboss.seam.core.ResourceLoader.instance(ResourceLoader.java:97)
              at org.jboss.seam.core.SeamResourceBundle.loadBundlesForCurrentLocale(SeamResourceBundle.java:58)
              at org.jboss.seam.core.SeamResourceBundle.getBundlesForCurrentLocale(SeamResourceBundle.java:48)
              at org.jboss.seam.core.SeamResourceBundle.handleGetObject(SeamResourceBundle.java:107)
              at java.util.ResourceBundle.getObject(ResourceBundle.java:319)
              at java.util.ResourceBundle.getString(ResourceBundle.java:285)
              at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:151)
              at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122)
              at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277)
              at com.sun.faces.util.Util.createInstance(Util.java:477)
              at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:636)
              at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:487)
              at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:381)
              at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
              at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
              at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1609)
              at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2764)
              at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
              at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
              at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
              at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
              at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
              at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
              at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
      



      This is a web application with components.xml in WEB-INF and seam.properties in WEB-INF/classes.  Any insight into what is causing this issue is very much appreciated.


      Thanks.