[ https://issues.jboss.org/browse/SEAMWICKET-16?page=com.atlassian.jira.plu... ] Asgeir Frimannsson commented on SEAMWICKET-16: ---------------------------------------------- I'm getting something similar (CR1 on JBoss AS 6.0.0.Final): HTTP Status 500 with {code} java.lang.IllegalStateException: Context is not active org.jboss.weld.context.AbstractConversationContext.deactivate(AbstractConversationContext.java:263) org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:125) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) java.lang.Thread.run(Thread.java:680) {code} It seems ConversationContext.deactivate() is called first in org.jboss.seam.wicket.SeamRequestCycle.detach() then afterwards in WeldListener.requestDestroyed... Shouldn't the deactivation only happen in WeldListener? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMWICKET-16?page=com.atlassian.jira.plu... ] Robert Reimann commented on SEAMWICKET-16: ------------------------------------------ In a forum discussion (http://seamframework.org/Community/Weld120Beta1#comment149514) Clint stated WELD-833 to be the root of SEAMWICKET-16. Is this issue fixed due to the resolution of WELD-833 in Weld 1.1.1 or does it require additional work within the Seam-Wicket module? The WELD-799 description contains a link to a hudson job that should test this issue: bq. There is a new hudson job which tests this at http://hudson.qa.jboss.com/hudson/view/Weld/job/perf-seam-wicket-numbergu... The link above seems to be dead - can anyone please point me to the current location of the test? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira