Session context destruction not working when session times out -------------------------------------------------------------- Key: WBRI-139 URL: https://jira.jboss.org/jira/browse/WBRI-139 Project: Web Beans RI Issue Type: Bug Affects Versions: 1.0.0.ALPHA2 Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Set session timeout to 1 in numberguess and wait java.lang.NullPointerException at org.jboss.webbeans.context.AbstractBeanMapContext.get(AbstractBeanMapContext.java:68) at org.jboss.webbeans.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:114) at org.jboss.webbeans.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:93) at org.jboss.webbeans.conversation.ServletConversationManager_$$_javassist_1.destroyAllConversations(ServletConversationManager_$$_javassist_1.java) at org.jboss.webbeans.servlet.ServletLifecycle.endSession(ServletLifecycle.java:90) at org.jboss.webbeans.servlet.WebBeansListener.sessionDestroyed(WebBeansListener.java:68) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:682) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:667) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1327) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1612) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1621) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1621) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1601) at java.lang.Thread.run(Thread.java:619) It appears as the beanmap returned from the session context threadlocal is null when the session has timed out -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira