[seam-issues] [JBoss JIRA] Commented: (SEAMWICKET-16) Weld in conjunction with Seam 3 Wicket throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients

[Asgeir Frimannsson (JIRA)]

    [ https://issues.jboss.org/browse/SEAMWICKET-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587387#comment-12587387 ] 

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?


> Weld in conjunction with Seam 3 Wicket throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SEAMWICKET-16
>                 URL: https://issues.jboss.org/browse/SEAMWICKET-16
>             Project: Seam for Apache Wicket
>          Issue Type: Bug
>         Environment: Affects version: 3.0.0-SNAPSHOT, Fix version: ?
>            Reporter: Martin Gencur
>
> This issue is the same as the linked one (WELD-799), only for Seam Wicket. Read the description there.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira