[richfaces-planning-issues] [JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception

[Matej Novotny (JIRA)]

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

Matej Novotny commented on RFPL-3878:
-------------------------------------

Indeed, that will do the trick, thanks [~jstefek]. I checked this and we use *2.2.6* - managed in {{richfaces/build/pom.xml}}. As for differences between RF and QA repo, I think metamer uses different mechanism for push test (synchronous?) hence this exception will not show. Nevertheless, updating Weld will resolve this and it seems to cause no additional problems.

In order to update Weld and to keep up with version used in WildFly, here is some information:
* WF 8.2 uses 2.2.6
** this version is too low and will cause these exceptions
* WF 9 uses 2.2.12
** its currently in CR2 so its likely to hit Final any time soon
** I think we should stick to version in WF 9



> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
>                 Key: RFPL-3878
>                 URL: https://issues.jboss.org/browse/RFPL-3878
>             Project: RichFaces Planning
>          Issue Type: Bug
>          Components: examples
>    Affects Versions: 4.5.6
>         Environment: Tomcat 8
> Showcase app
> Mojarra
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 4.5.7
>
>
> When running Showcase push tests, there are exceptions in the log. Here is an  example of one:  
> {code}
> 02:36:37 SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
> 02:36:37 java.lang.IllegalStateException: WELD-000335: Context is already active
> 02:36:37 	at org.jboss.weld.context.http.LazyHttpConversationContextImpl.activate(LazyHttpConversationContextImpl.java:57)
> 02:36:37 	at org.jboss.weld.servlet.ConversationContextActivator.activate(ConversationContextActivator.java:107)
> 02:36:37 	at org.jboss.weld.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:93)
> 02:36:37 	at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:225)
> 02:36:37 	at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:160)
> 02:36:37 	at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestInitialized(ForwardingServletListener.java:42)
> 02:36:37 	at org.apache.catalina.core.StandardContext.fireRequestInitEvent(StandardContext.java:5902)
> 02:36:37 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 02:36:37 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> 02:36:37 	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> 02:36:37 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> 02:36:37 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> 02:36:37 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> 02:36:37 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> 02:36:37 	at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> 02:36:37 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> 02:36:37 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> 02:36:37 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 02:36:37 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 02:36:37 	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 02:36:37 	at java.lang.Thread.run(Thread.java:745)
> {code}
> [Here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5-showcase-ftest-mojarra-server-compatibility/53/SERVER=tomcat8,jdk=java17_default,label=brFF31&&!macosx&&!vmg05-w2012-x86-64/consoleFull] is a sample of Jenkins job, where there is such exception. Just switch to full log and CTRL+ F for "Context is already active".
> It does not affect the test results - CDI push test still passes (the other one - for UUID -  is problematic/unstable because it measures time).
> What I found out so far:
> * Cannot be reproduced with Metamer (neither via automated nor manual way)
> * Only appears when server is started via Arq. (e.g. not manually) meaning this is likely to be a configuration issue. Once started manually, one can do exactly what the test does but never gets the exception.
> * Configs used for Tomcat are:
> ** tomcat-users.xml -> copied over from build resources, does not affect it
> ** arquillian.xml -> tried to temper with settings, changed for those in QA repo (there are slight differences) but to no avail
> ** tried to start tomcat manually with the above settings, but still cannot reproduce it
> * I checked the related WELD issue (335), but that was resolved long ago, we are using 2.2.6 version atm (in all repos)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)