[
https://issues.jboss.org/browse/WFCORE-2656?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2656:
------------------------------------------
Do you see this when it passes?
2017-04-14 20:02:40,251 ERROR [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) WFLYDS0012: Scan of
/home/ehsavoie/dev/wildfly/core/testsuite/standalone/target/dummy threw Exception:
java.lang.RuntimeException: WFLYDS0036: Deployment model operation failed. WFLYCTL0271:
Operation cancelled
I don't have any particular theory as to why that's relevant, other than it
involves a separate management client thread interacting with the system in the middle of
everything.
If you stick a trace in CapabilityRegistry.publish and .rollback that may show something
further.
DeploymentTestCase.testFilesystemScannerRegistration fails
intermittently
-------------------------------------------------------------------------
Key: WFCORE-2656
URL:
https://issues.jboss.org/browse/WFCORE-2656
Project: WildFly Core
Issue Type: Bug
Components: Deployment Scanner, Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&...
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)