Smiling... well, that's not really the whole stack trace. I just wanted to show you bits and pieces, enough to justify this email/topic.
Is it in order to create a JIRA for this and add a 'full' stacktrace? On Tue, Nov 27, 2012 at 9:32 AM, Mark Struberg <strub...@yahoo.de> wrote: > Oki, with the full stack trace this makes even more sense. > > This happens becasue the JSF specified ServletContainerInitializer is > booting MyFaces. And MyFaces kicks up CODI. As there is no guaranteed boot > order we do some nasty tricks to guarantee the right sequence. And that > might touch some SessionBean. > I finally need to debug into that and get rid of this warning in CODI. But > this is nothing to worry about. > > LieGrue, > strub > > > > > ----- Original Message ----- > > From: "Howard W. Smith, Jr." <smithh032...@gmail.com> > > To: users@openejb.apache.org > > Cc: > > Sent: Tuesday, November 27, 2012 7:30 AM > > Subject: Re: WARNING: Could NOT lazily initialize session context > because of null RequestContext > > > > Okay, I see this warning even on startup of container. see below. > > Evidently, nothing to be concerned about, but for some reason, TomEE > WARNS > > developer about this. > > > > *1st occurrence* > > INFO: using context file > > C:\Users\Public\NetBeansProjects\mcms\build\web\META-INF\context.xml > > Nov 27, 2012 1:20:58 AM org.apache.openejb.assembler.classic.Assembler > > createApplication > > INFO: Deployed > > Application(path=C:\Users\Public\NetBeansProjects\mcms\build\web) > > Nov 27, 2012 1:20:59 AM org.apache.openejb.cdi.CdiAppContextsService > > lazyStartSessionContext > > *WARNING: Could NOT lazily initialize session context because of null > > RequestContext* > > Nov 27, 2012 1:21:00 AM > > org.apache.myfaces.config.DefaultFacesConfigurationProvider > > getStandardFacesConfig > > INFO: Reading standard config META-INF/standard-faces-config.xml > > Nov 27, 2012 1:21:00 AM > > org.apache.myfaces.config.DefaultFacesConfigurationProvider > > getWebAppFacesConfig > > INFO: Reading config /WEB-INF/faces-config.xml > > Nov 27, 2012 1:21:00 AM > > org.apache.myfaces.config.DefaultFacesConfigurationProvider > > getClassloaderFacesConfig > > > > *2nd occurrence* > > INFO: Deployed > > Application(path=C:\Users\Public\NetBeansProjects\mcms\build\web) > > Nov 27, 2012 1:21:21 AM org.apache.openejb.cdi.CdiAppContextsService > > lazyStartSessionContext > > *WARNING: Could NOT lazily initialize session context because of null > > RequestContext* > > Nov 27, 2012 1:21:22 AM > > org.primefaces.webapp.PostConstructApplicationEventListener processEvent > > INFO: Running on PrimeFaces 3.5-SNAPSHOT > > Nov 27, 2012 1:21:22 AM > > > org.primefaces.extensions.application.PostConstructApplicationEventListener > > processEvent > > INFO: Running on PrimeFaces Extensions 0.6.1 > > > > > > > > On Tue, Nov 27, 2012 at 1:06 AM, Romain Manni-Bucau > > <rmannibu...@gmail.com>wrote: > > > >> Means you use sessionscoped bean when there is no more request i think > >> Le 27 nov. 2012 04:05, "Howard W. Smith, Jr." > > <smithh032...@gmail.com> a > >> écrit : > >> > >> > Why is this message in my server console/log? Is this TomEE's way > > of > >> > closing sessions due to some type of timeout based on inactivity? > >> > > >> > Nov 26, 2012 7:26:34 PM org.apache.openejb.cdi.CdiAppContextsService > >> > lazyStartSessionContext > >> > WARNING: Could NOT lazily initialize session context because of null > >> > RequestContext > >> > > >> > > >
