This also happens sometimes if the container boots and some eagerly created bean (e.g. @Startup) touches a @SessionScoped bean. Obviously there is no session at container boot...
LieGrue, strub ----- Original Message ----- > From: Romain Manni-Bucau <rmannibu...@gmail.com> > To: users@openejb.apache.org > Cc: > Sent: Tuesday, November 27, 2012 7:06 AM > Subject: Re: WARNING: Could NOT lazily initialize session context because of > null RequestContext > > 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 >> >
