Deryk Sinotte added a comment - 20/Mar/13 11:27 AM Not sure why the older case was marked fixed. This doesn't seem to be easy to replicate with our standard examples. As per the original customer comments, my theory was that the session had to be created and invalidated outside of most of the ICEfaces processing. Our SessionExpiredListener will still operate in this type of environment but the majority of the WindowScope processing will not meaning the appropriate "state" is never added to the session. To mimic this behaviour, I simply changed the index.jsp of our basic example to: <% session.setAttribute( "foo" , "bar" ); session.invalidate(); response.sendRedirect( "icefaces.jsf" ); %> Doing this creates a session and invalidates it before the WindowScopeManager has a chance to set things up. However, our SessionExpiredListener still runs so then you get the following logged: Mar 20, 2013 10:11:39 AM org.icefaces.impl.application.SessionExpiredListener sessionDestroyed WARNING: An exception occurred while trying to invoke @PreDestroy on window scoped beans: null There are a couple of things we could do: 1) Since the log is at WARNING level, we could just turn this down as the involved code is basically already doing its job in catching the exception and moving on: try { // Not everything might be available to us anymore from the session, causing a possible exception. WindowScopeManager.disposeWindows(session); } catch (Exception exception) { LOGGER.log( Level.WARNING, "An exception occurred while trying to invoke @PreDestroy on window scoped beans: " + exception.getMessage()); } 2) Deal with the NullPointerException at the source as I originally suggested: public static void disposeWindows( final HttpSession session) { // The strategy is to invoke @PreDestroy on as many applicable window scoped beans as possible and not to bail // out on the first fail. State state = (State) session.getAttribute(WindowScopeManager.class.getName()); //ICE-9071: It's possible for a session to expire without a WindowScopeManager if the session was created and //invalidated without the WindowScopeManager doing it's thing (i.e. no JSF lifecycle). if (state == null ){ return ; } notifyPreDestroyForAll(state.windowScopedMaps.values()); notifyPreDestroyForAll(state.disposedWindowScopedMaps); } For now I've opted for #2 and left the log level at WARNING as it may catch other behaviours we want to know about.