[teiid-issues] [JBoss JIRA] (TEIID-4966) Infinite loop when deploying a malformed vdb

[ https://issues.jboss.org/browse/TEIID-4966?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4966: --------------------------------------- I'm not seeing infinite loop behavior. If I leave the malformed file in place, the log will report in approximately one minute: 15:39:51,106 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0021: Deployment content /home/shawkins/workspaces/teiid-git/teiid/test-integration/common/target/teiid-10.0.0.Alpha1-SNAPSHOT/standalone/deployments/test-vdb.xml appears to be incomplete and is not progressing toward completion. This content cannot be auto-deployed. 15:39:51,107 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0014: Scan found content configured for auto-deploy that could not be safely auto-deployed. See details above. Deployment changes will not be processed until all problematic content is either removed or whether to deploy the content or not is indicated via a .dodeploy or .skipdeploy marker file. Problematic deployments are [test-vdb.xml] 15:39:51,114 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0002: Cannot remove extraneous deployment marker file test-vdb.xml.pending If I update the file, deployment will complete as expected. However I do agree that the logging is noisy for an invalid xml for a full minute. I don't see anywhere in our logic where we are instigating a retry, so there may need to be an issue against WildFly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)