To confirm what i mentioned in previous email below (my loginfilter should not be responsible for 2 calls to @PreDestroy). See server log below. You might want to look at the code in org.apache.openejb.cdi.CdiAppContextsService lazyStartSessionContext, and see why this is called or at what point is this called by container or in lifecycle. Look for next email, have an idea, something else to add to the log. :)
INFO: Server startup in 27176 ms LoginFilter.doFilter(): session = NOT null LoginFilter.doFilter(): pf_usersController = NOT null LoginFilter.doFilter(): req.getRequestURI() = /mcmsweb/login.jsf LoginFilter.doFilter(): ajaxRequest = false; ajaxHeader = null LoginFilter.doFilter(): agent.getUserAgent() = mozilla/5.0 (windows nt 6.0; wow64) applewebkit/537.11 (khtml, like gecko) chrome/23.0.1271.95 safari/537.11 Dec 07, 2012 3:54:55 AM org.apache.myfaces.el.unified.ResolverBuilderBase sortELResolvers INFO: Chain of EL resolvers for Faces sorted with: org.apache.myfaces.el.unified.OpenWebBeansELResolverComparator@1e233895 and the result order is [org.apache.myfaces.el.unified.resolver.implicitobject.ImplicitObjectResolver@1a57cda8, org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver@7a7ede1a, org.apache.myfaces.el.FlashELResolver@1f27bbca, org.apache.myfaces.el.unified.resolver.ManagedBeanResolver@6999dac0, org.apache.myfaces.el.unified.resolver.ResourceResolver@73e8a969, javax.el.ResourceBundleELResolver@2fca67f2, org.apache.myfaces.el.unified.resolver.ResourceBundleResolver@116e5961, javax.el.MapELResolver@63adf837, javax.el.ListELResolver@32831601, javax.el.ArrayELResolver@3c19b58f, javax.el.BeanELResolver@3bdede1c, org.apache.webbeans.el.WebBeansELResolver@24c81ef9] LoginFilter.doFilter(): session = NOT null LoginFilter.doFilter(): pf_usersController = NOT null LoginFilter.doFilter(): req.getRequestURI() = /mcmsweb/login.jsf LoginFilter.doFilter(): ajaxRequest = false; ajaxHeader = null [EL Info]: 2012-12-07 03:55:03.682--ServerSession(1877145955)--EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461 [EL Info]: 2012-12-07 03:55:04.262--ServerSession(1877145955)--file:/C:/apache-tomee-plus-1.5.1-SNAPSHOT/webapps/mcmsweb/WEB-INF/classes/_mcmsPU login successful GoogleCalendarUtil: calendarList.getEntries().size() = 2 GoogleCalendarUtil: calendar ID/summary = oleta...@gmail.com/mcmsweb GoogleCalendarUtil: calendar ID/summary = 998449989...@developer.gserviceaccount.com/998449989...@developer.gserviceaccount.com GoogleCalendarUtil: events.getItems().size() = 250 pf_UsersController.loginUser(): brian logged in at Fri Dec 07 03:55:04 EST 2012 LoginFilter.doFilter(): session = NOT null LoginFilter.doFilter(): pf_usersController = NOT null LoginFilter.doFilter(): req.getRequestURI() = /mcmsweb/index.jsf LoginFilter.doFilter(): ajaxRequest = false; ajaxHeader = null LoginFilter.doFilter(): session = NOT null LoginFilter.doFilter(): pf_usersController = NOT null LoginFilter.doFilter(): req.getRequestURI() = /mcmsweb/javax.faces.resource/images/ui-bg_white-lines_85_f7f7ba_40x100.png.jsf LoginFilter.doFilter(): ajaxRequest = false; ajaxHeader = null LoginFilter.doFilter(): session = NOT null LoginFilter.doFilter(): pf_usersController = NOT null LoginFilter.doFilter(): req.getRequestURI() = /mcmsweb/pf_viewExpired.jsf LoginFilter.doFilter(): ajaxRequest = false; ajaxHeader = null pf_UsersController.sessionTimeout(): brian session ended at Fri Dec 07 03:56:23 EST 2012 Dec 07, 2012 3:58:08 AM org.apache.openejb.cdi.CdiAppContextsService lazyStartSessionContext WARNING: Could NOT lazily initialize session context because of null RequestContext On Fri, Dec 7, 2012 at 3:33 AM, Howard W. Smith, Jr. <smithh032...@gmail.com > wrote: > Honestly, i 'do' have a servlet filter in place that @Inject > pf_UserController, but please note/remember... session timed out due to > session timeout value in web.xml, @PreDestroy is invoked, and then > @PreDestroy is invoked again... no other code is called in between. > > I really don't think my servlet filter (login filter) is responsible for > @PreDestroy being called a 2nd time. > > let me turn on debug = true in my login/servlet filter and see what > happens between 1st and 2nd call to @PreDestroy. > >
