Bug 1076015
| Summary: | Multicast-based clustering testsuite does not work on JDK 8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Pavel Jelinek <pjelinek> | ||||
| Component: | Clustering, Testsuite | Assignee: | Radoslav Husar <rhusar> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitka Kozana <jkudrnac> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3.0 | CC: | bban, jkudrnac, kkhan, mkopecky, pjelinek, pkremens, rhusar | ||||
| Target Milestone: | DR6 | ||||||
| Target Release: | EAP 6.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | Clustering testsuite | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1167666 (view as bug list) | Environment: |
OpenJDK1.8, OracleJDK1.8
|
||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1104190, 1167666 | ||||||
| Attachments: |
|
||||||
|
Description
Pavel Jelinek
2014-03-13 11:44:50 UTC
Created attachment 873985 [details]
logs
Other exception in jbossas-clustering-SYNC-tcp-1/standalone/log/server.log : 04:52:17,904 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 65) MODCLUSTER000002: Initiating mod_cluster shutdown 04:52:17,918 INFO [org.apache.coyote.http11.Http11NioProtocol] (MSC service thread 1-2) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.180.50:8180 04:52:17,918 INFO [org.apache.coyote.http11.Http11NioProtocol] (MSC service thread 1-2) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.180.50:8180 04:52:17,919 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] 04:52:17,923 ERROR [org.apache.tomcat.util.net] (http-/10.16.180.50:8180-Acceptor) JBWEB003011: Error allocating socket processor: java.util.concurrent.RejectedExecutionException: Task org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor@120c52eb rejected from java.util.concurrent.ThreadPoolExecutor@17fae263[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) [rt.jar:1.8.0] at org.apache.tomcat.util.net.NioEndpoint.processChannel(NioEndpoint.java:453) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:566) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] Please retest with a stable JDK release, you are using slighly old build of JDK (namely 1.8.0-b128). RejectedExecutionException is unrelated. DR4 runs on same machine dev132-rhel7-virt2 with just different JDKs: JDK1.7: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL7-matrix-OracleJDK/jdk=java17_default,label_exp=EAP-RHEL7/14/testReport/ JDK1.8: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL7-matrix-OracleJDK/jdk=java18_default,label_exp=EAP-RHEL7/12/testReport/ The builds are still using b128. Please retest with the latest version od JDK 1.8, it makes no sense to test with pre-released versions of JDK. Do you guys have a box running on RHEL 7 which I could use to test JGroups ? I'm downloading the ISO image of RHEL 7 and will try to run it on VirtualBox... See same results on OracleJDK 1.8 GA: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL7-matrix-OracleJDK/jdk=java18_default,label_exp=EAP-RHEL7/18/testReport/ The results are no longer accessible - HTTP Status 404. Please make sure to mark "keep this build forever" if you link it to an issue tracker. (Nevertheless, I tried to reproduce the issue but the testsuite run correctly on RHEL7/latest Oracle JDK.) It's still regularly happening. See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-RHEL-matrix-OracleJDK8/jdk=jdk1.8,label_exp=EAP-RHEL7/19/testReport/ for test results and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-RHEL-matrix-OracleJDK8/jdk=jdk1.8,label_exp=EAP-RHEL7/19/artifact/archive.zip for logs. Both nodes are started but they don't know about each other. How do you specify -Dnode0 and -Dnode1 testsuite parameters? Sometimes this issue occures on RHEL releases as well but only occasionally. See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-RHEL-matrix-OracleJDK8-SM/1/jdk=jdk1.8,label_exp=RHEL6%26%26x86_64/testReport/ We can see this also with latest jdk https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-RHEL-matrix-OracleJDK8-SM/6/jdk=jdk1.8,label_exp=EAP-RHEL7/testReport/junit/org.jboss.as.test.clustering.cluster.web/ java version "1.8.0_20" Java(TM) SE Runtime Environment (build 1.8.0_20-b26) Java HotSpot(TM) Server VM (build 25.20-b23, mixed mode) Try to reproduce with -Dnode0 != -Dnode1 where (on testing machine: dev136-virt1) $ echo $MYTESTIP_1 10.16.180.15 $ echo $MYTESTIP_2 10.16.180.182 JDK8 ./integration-tests.sh -Dts.noSmoke -Dts.clust -Dtest=org.jboss.as.test.clustering.cluster.web.* tests pass ./integration-tests.sh -Dts.noSmoke -Dts.clust -Dtest=org.jboss.as.test.clustering.cluster.web.* -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 tests fail JDK7 ./integration-tests.sh -Dts.noSmoke -Dts.clust -Dtest=org.jboss.as.test.clustering.cluster.web.* -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 tests pass I can reproduce the problem on a single machine but with different IP bind addresses. The problem does not occur on JDK 7 with the same configuration and does not occur if binding to the same address (using port offset). Investigating. Same problem with OpenJDK8 and OracleJDK8u40. Bela Ban <bela> updated the status of jira JGRP-1878 to Resolved Verified on EAP 6.4.0.DR9 |