<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Thank you for this tip, should be resolved in 3.5,
but for the moment, how to modify the jboss timeout deployment?</font><br>
<div class="moz-cite-prefix">Le 26/05/2014 14:45, John Taylor a
écrit :<br>
</div>
<blockquote
cite="mid:CAGd4S1RP4PVP595x6R4SbSYk9c-kRtQxb=SZXcRGsBXyNbB5XQ@mail.gmail.com"
type="cite">
<pre wrap="">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.
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1078291">https://bugzilla.redhat.com/show_bug.cgi?id=1078291</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2014-May/024297.html">http://lists.ovirt.org/pipermail/users/2014-May/024297.html</a>
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
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
<a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre>
</body>
</html>