[ovirt-users] jboss deployments timeout (was: getting 404 after fresh install of oVirt 3.4 on CentOS 6.5 (+ solution))

[John Taylor]

Didi,

Some background is that I first ran into this when I added dwh+reports
to my 3.4 setup, and I found your bz then and did the fix (with
changes below) and it worked for me. The fixed ovirt-engine.xml.in got
overwritten when I upgraded to 3.4.1 and I reapplied .

But I did change
<deployment-scanner scan-interval="5000" path="$tempdir/deployments"/
deployment-timeout="1200">
to
<deployment-scanner scan-interval="5000" path="$tempdir/deployments"
deployment-timeout="1200"/>

i.e. the / looks to be misplaced and should be used to close the
deployment-scanner tag.

>>If you do, please report - what exact versions (OS, jboss, ovirt, etc) you use
fedora 19 w/ latest updates
 kernel-3.13.11-100.fc19.x86_64
 ovirt-engine-3.4.1-1.fc19.noarch
 jboss-as-7.1.1-21.fc19.noarch
 ovirt-engine-reports-3.4.1-1.fc19.noarch

>>and (according to the logs) how long did the deployment take. Thanks!
My last startup shows that was right at the 59 second mark. So you can
see I'm right on the edge of it failing with default timeout of 60
seconds.

from server.log
2014-05-12 23:22:00,463 INFO  [org.jboss.as.server.deployment] (MSC
service thread 1-5) JBAS015876: Starting deployment of "engine.ear"
2014-05-12 23:22:00,464 INFO  [org.jboss.as.server.deployment] (MSC
service thread 1-6) JBAS015876: Starting deployment of
"ovirt-engine-reports.war"
...
2014-05-12 23:22:59,383 INFO  [org.jboss.as.server]
(DeploymentScanner-threads - 2) JBAS018559: Deployed "engine.ear"
2014-05-12 23:22:59,385 INFO  [org.jboss.as.server]
(DeploymentScanner-threads - 2) JBAS018559: Deployed
"ovirt-engine-reports.war"

Thanks,
-John