Weld throws java.lang.IllegalStateException: Context is not active during
stress testing at higher number of clients
--------------------------------------------------------------------------------------------------------------------
Key: WELD-799
URL: https://issues.jboss.org/browse/WELD-799
Project: Weld
Issue Type: Bug
Components: Performance and Scalability
Affects Versions: 1.1.0.CR1
Environment: JBossAS 6 CR1, Weld/trunk
Reporter: Martin Gencur
Fix For: 1.1.0.Final
I executed performance stress test using Wicket for view layer and Weld-trunk.
Everything goes well up to 2100 sessions. Then the following exception is
thrown. I tried it twice and it failed at the same amount of sessions.
Whole stack trace:
2010-12-17 03:03:57,840 WARN
[org.apache.wicket.protocol.http.pagestore.FileChannelPool]
(http-10.16.89.196-8080-304) Unable to reduce enough channels, no idle channels
left to remove.
2010-12-17 03:03:57,842 WARN
[org.apache.wicket.protocol.http.pagestore.FileChannelPool]
(PageSavingThread-Wicket Filter) Unable to reduce enough channels, no idle
channels left to remove.
2010-12-17 03:03:57,842 WARN
[org.apache.wicket.protocol.http.pagestore.FileChannelPool]
(PageSavingThread-Wicket Filter) Unable to reduce enough channels, no idle
channels left to remove.
2010-12-17 03:03:58,499 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seam-wicket-examples-numberguess-3.0.0-SNAPSHOT]]
(http-10.16.89.196-8080-6) Exception sending request destroyed lifecycle event
to listener instance of class org.jboss.weld.servlet.WeldListener:
java.lang.IllegalStateException: Context is not active
at
org.jboss.weld.context.AbstractConversationContext.deactivate(AbstractConversationContext.java:263)
[:2010-12-17 02:45]
at
org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:125)
[:2010-12-17 02:45]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:204)
[:6.0.0.20101110-CR1]
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181)
[:6.0.0.20101110-CR1]
at
org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285)
[:1.1.0.Final]
at
org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261)
[:1.1.0.Final]
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88)
[:6.0.0.20101110-CR1]
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100)
[:6.0.0.20101110-CR1]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
[:6.0.0.20101110-CR1]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[:6.0.0.20101110-CR1]
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
[:6.0.0.20101110-CR1]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[:6.0.0.20101110-CR1]
at
org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53)
[:6.0.0.20101110-CR1]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
[:6.0.0.20101110-CR1]
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[:6.0.0.20101110-CR1]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
[:6.0.0.20101110-CR1]
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
[:6.0.0.20101110-CR1]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
There is a new hudson job which tests this at
http://hudson.qa.jboss.com/hudson/view/Weld/job/perf-seam-wicket-numberguess-single
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
