-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR16
-
None
-
Regression
-
-
-
-
-
-
Description of problem:
DeploymentTestCase.testFilesystemScannerRegistration fails intermittently
This is regression against EAP 7.1.0.DR15
How reproducible:
40%, but reproducer job can reproduce this issue with 90% probability
Steps to Reproduce:
export SETTINGS_XML=`pwd`/tools/maven/conf/settings.xml cd testsuite for (( i = 1; i <= 100 ; i++ )) ; do echo $i mvn install -DfailIfNoTests=false -B -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -s $SETTINGS_XML -llr -DfailIfNoTests=false "-Dtest=DeploymentTestCase#testFilesystemScannerRegistration" done
Actual results:
StackTrace:
org.junit.ComparisonFailure: { "outcome" => "failed", "failure-description" => "WFLYCTL0436: Cannot register capability 'org.wildfly.management.deployment-scanner.dummy' at location '[ (\"subsystem\" => \"deployment-scanner\"), (\"scanner\" => \"dummy\") ]' as it is already registered in context 'global' at location(s) '[[ (\"subsystem\" => \"deployment-scanner\"), (\"scanner\" => \"dummy\") ]]'", "rolled-back" => true } expected:<[success]> but was:<[failed]> at org.junit.Assert.assertEquals(Assert.java:115) at org.wildfly.core.test.standalone.mgmt.api.DeploymentTestCase.addDeploymentScanner(DeploymentTestCase.java:817) at org.wildfly.core.test.standalone.mgmt.api.DeploymentTestCase.addDeploymentScanner(DeploymentTestCase.java:799) at org.wildfly.core.test.standalone.mgmt.api.DeploymentTestCase.testFilesystemScannerRegistration(DeploymentTestCase.java:253)
Standard output:
&#27;[0m11:37:57,471 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6-redhat-1 &#27;[0m&#27;[0m11:37:58,072 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1 &#27;[0m&#27;[0m11:37:58,241 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Core 3.0.0.Beta13-redhat-1 "Kenny" starting &#27;[0m&#27;[0m11:37:59,185 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. &#27;[0m&#27;[0m11:37:59,239 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) &#27;[0m&#27;[0m11:37:59,354 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.5.0.Beta4-redhat-1 &#27;[0m&#27;[0m11:37:59,366 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.5.0.Beta4-redhat-1 &#27;[0m&#27;[0m11:37:59,531 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none &#27;[0m&#27;[33m11:37:59,596 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore /mnt/hudson_workspace/workspace/eap-7x-as-testsuite-test-core-rhel-deployment-test-case/1cfa62fc/testsuite/standalone/target/wildfly-core/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost &#27;[0m&#27;[0m11:37:59,608 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Beta19-redhat-1 &#27;[0m&#27;[33m11:37:59,818 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-3) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console &#27;[0m&#27;[0m11:38:00,002 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server &#27;[0m&#27;[0m11:38:00,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management &#27;[0m&#27;[0m11:38:00,006 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 &#27;[0m&#27;[0m11:38:00,006 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Beta13-redhat-1 "Kenny" started in 3253ms - Started 60 of 63 services (20 services are lazy, passive or on-demand) &#27;[0m&#27;[0m11:38:00,516 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /mnt/hudson_workspace/workspace/eap-7x-as-testsuite-test-core-rhel-deployment-test-case/1cfa62fc/testsuite/standalone/target/dummy &#27;[0m
Expected results:
No error
Upstream description (WFCORE-2656 ):
https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&testNameId=5510538220891037036&tab=testDetails
I fear this has something to do with the capability registry and nothing to do with the scanner itself. It started happening when I added a capability to the scanner so it could consume a capability for the path it references.
The test does a quick add/remove/add of a scanner resource and it's the 2nd add that fails with a dupicate capability error. But the remove mean the dup is gone. It's intermittent so I fear some race, but there's nothing obvious.
- clones
-
WFCORE-2656 DeploymentTestCase.testFilesystemScannerRegistration fails intermittently
- Resolved
- is incorporated by
-
JBEAP-10119 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta16
- Closed