[JBoss JIRA] (RFPL-3879) Review framework tests using Warp
by Pavol Pitonak (JIRA)
Pavol Pitonak created RFPL-3879:
-----------------------------------
Summary: Review framework tests using Warp
Key: RFPL-3879
URL: https://issues.jboss.org/browse/RFPL-3879
Project: RichFaces Planning
Issue Type: Task
Components: QE
Affects Versions: 4.5.6
Reporter: Pavol Pitonak
Assignee: Jiří Štefek
There are few framework tests that use Arquillian Warp and all of them fail, probably caused by ARQ-1952.
Unless there is some developer's activity in Arquillian Warp, feel free to remove tests covered in Metamer or rewrite without using Warp if not covered in Metamer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (RFPL-3692) metamer: stabilize push tests
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3692?page=com.atlassian.jira.plugin.... ]
Jiří Štefek resolved RFPL-3692.
-------------------------------
Resolution: Done
> metamer: stabilize push tests
> -----------------------------
>
> Key: RFPL-3692
> URL: https://issues.jboss.org/browse/RFPL-3692
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 4.5.1.Final
> Environment: Firefox
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.7
>
>
> Only on *Firefox*.
> Sometimes, running these tests freezes the whole suite inside one test method.
> Log from Jenkins (check the times):
> {code}
> 06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> 09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
> 09:11:18.003 Terminating xvnc.
> 09:11:18.011 $ vncserver -kill :41
> 09:11:18.144 Killing Xvnc process ID 20637
> 09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> {code}
> It could be also reproduced locally by e.g.:
> {{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
> It is hard to reproduce it sometimes, so try to run it repeatedly (you can add {{-Drepeats=10}}).
> It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (RFPL-3692) metamer: stabilize push tests
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3692?page=com.atlassian.jira.plugin.... ]
Jiří Štefek updated RFPL-3692:
------------------------------
Fix Version/s: 4.3.7
> metamer: stabilize push tests
> -----------------------------
>
> Key: RFPL-3692
> URL: https://issues.jboss.org/browse/RFPL-3692
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 4.5.1.Final
> Environment: Firefox
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.7
>
>
> Only on *Firefox*.
> Sometimes, running these tests freezes the whole suite inside one test method.
> Log from Jenkins (check the times):
> {code}
> 06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> 09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
> 09:11:18.003 Terminating xvnc.
> 09:11:18.011 $ vncserver -kill :41
> 09:11:18.144 Killing Xvnc process ID 20637
> 09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> {code}
> It could be also reproduced locally by e.g.:
> {{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
> It is hard to reproduce it sometimes, so try to run it repeatedly (you can add {{-Drepeats=10}}).
> It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (RFPL-3692) metamer: stabilize push tests
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3692?page=com.atlassian.jira.plugin.... ]
Jiří Štefek commented on RFPL-3692:
-----------------------------------
Looks good after issues RF-13949 and RF-14044 were resolved. Removed the waiting time.
> metamer: stabilize push tests
> -----------------------------
>
> Key: RFPL-3692
> URL: https://issues.jboss.org/browse/RFPL-3692
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 4.5.1.Final
> Environment: Firefox
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.7
>
>
> Only on *Firefox*.
> Sometimes, running these tests freezes the whole suite inside one test method.
> Log from Jenkins (check the times):
> {code}
> 06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> 09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
> 09:11:18.003 Terminating xvnc.
> 09:11:18.011 $ vncserver -kill :41
> 09:11:18.144 Killing Xvnc process ID 20637
> 09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> {code}
> It could be also reproduced locally by e.g.:
> {{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
> It is hard to reproduce it sometimes, so try to run it repeatedly (you can add {{-Drepeats=10}}).
> It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (RFPL-3692) metamer: stabilize push tests
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3692?page=com.atlassian.jira.plugin.... ]
Jiří Štefek updated RFPL-3692:
------------------------------
Description:
Only on *Firefox*.
Sometimes, running these tests freezes the whole suite inside one test method.
Log from Jenkins (check the times):
{code}
06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
09:11:18.003 Terminating xvnc.
09:11:18.011 $ vncserver -kill :41
09:11:18.144 Killing Xvnc process ID 20637
09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
{code}
It could be also reproduced locally by e.g.:
{{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
It is hard to reproduce it sometimes, so try to run it repeatedly (you can add {{-Drepeats=10}}).
It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
was:
Only on *Firefox*.
Sometimes, running these tests freezes the whole suite inside one test method.
Log from Jenkins (check the times):
{code}
06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
09:11:18.003 Terminating xvnc.
09:11:18.011 $ vncserver -kill :41
09:11:18.144 Killing Xvnc process ID 20637
09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
{code}
It could be also reproduced locally by e.g.:
{{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
It is hard to reproduce it sometimes, so try to run it repeatedly.
It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
> metamer: stabilize push tests
> -----------------------------
>
> Key: RFPL-3692
> URL: https://issues.jboss.org/browse/RFPL-3692
> Project: RichFaces Planning
> Issue Type: Task
> Components: QE
> Affects Versions: 4.5.1.Final
> Environment: Firefox
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
>
> Only on *Firefox*.
> Sometimes, running these tests freezes the whole suite inside one test method.
> Log from Jenkins (check the times):
> {code}
> 06:26:31.869 [09:10:00] STARTED: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> 09:11:17.998 Build timed out (after 180 minutes). Marking the build as aborted.
> 09:11:18.003 Terminating xvnc.
> 09:11:18.011 $ vncserver -kill :41
> 09:11:18.144 Killing Xvnc process ID 20637
> 09:11:18.281 [11:54:46] FAILURE: a4jPush.TestTwoPushCDI.testPushEnable() { template=plain }
> {code}
> It could be also reproduced locally by e.g.:
> {{mvn verify -Dbrowser=firefox -DexcludedGroups=extended,Future -Dtemplates=* -Pwildfly-managed-8-2 -Dtest=TestTwoPush#testOnSubscribed}}
> It is hard to reproduce it sometimes, so try to run it repeatedly (you can add {{-Drepeats=10}}).
> It will stuck on this line [*Graphene.waitModel().until().element(page.getRequestTimeElement()).text().not().equalTo(requestTime);*|https://github.com/richfaces/richfaces-qa/blob/master/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/a4jPush/TestTwoPush.java#L60].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Jiří Štefek commented on RFPL-3878:
-----------------------------------
Hi [~manovotn], nice catch.
I have found similar WELD issue -- WELD-1774, which was resolved in WELD *2.2.8*. I have tried to run the tests with the mentioned version and it seems to solve this problem.
> 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
>
> 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...] 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)
10 years, 7 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny updated RFPL-3878:
--------------------------------
Environment:
Tomcat 8
Showcase app
Mojarra
was:
Tomcat 8
Showcase app
> 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
>
> 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...] 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)
10 years, 7 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny updated RFPL-3878:
--------------------------------
Steps to Reproduce:
* Go to your RF repository
* Make sure you are on master
* navigate to {{examples/showcase}}
* Run the following command:
** {{mvn clean verify -Dintegration=tomcat8 -Dbrowser=firefox -Dtest=ITestPushCdi}}
* See the log in terminal, as the test executes, the exception appears several times and in the end the test succeeds
Component/s: examples
> 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
> Reporter: Matej Novotny
>
> 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...] 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)
10 years, 7 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3878:
-------------------------------------
[~jstefek], [~ppitonak] if you have any clue what might possibly cause this, please leave a comment.
> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
> Key: RFPL-3878
> URL: https://issues.jboss.org/browse/RFPL-3878
> Project: RichFaces Planning
> Issue Type: Bug
> Affects Versions: 4.5.6
> Environment: Tomcat 8
> Showcase app
> Reporter: Matej Novotny
>
> 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...] 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)
10 years, 7 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
Matej Novotny created RFPL-3878:
-----------------------------------
Summary: Showcase & Tomcat & Push - Context already active exception
Key: RFPL-3878
URL: https://issues.jboss.org/browse/RFPL-3878
Project: RichFaces Planning
Issue Type: Bug
Affects Versions: 4.5.6
Environment: Tomcat 8
Showcase app
Reporter: Matej Novotny
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...] 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)
10 years, 7 months