Re: [ovirt-users] issued engine-report with 3.4

Hi Guys, I think this is the deployment timeout problem. What's happening is that jboss is timing out the deployment now that it's taking longer than 60 seconds. The same thing happened to me when I added dwh+reports. https://bugzilla.redhat.com/show_bug.cgi?id=1078291 http://lists.ovirt.org/pipermail/users/2014-May/024297.html 2014-05-23 17:59:22,375 INFO [stdout] (MSC service thread 1-4) Creating ActionModelService object. 2014-05-23 17:59:22,381 INFO [stdout] (MSC service thread 1-4) Creating action model infrastructure. 2014-05-23 17:59:32,112 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 2014-05-23 17:59:32,116 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ovirt-engine-reports.war" was rolled back with failure message Operation cancelled 2014-05-23 17:59:32,117 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "engine.ear" was rolled back with no failure message 2014-05-23 17:59:32,126 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 2014-05-23 17:59:32,455 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED -John