Bug #10769

Add a new CLI script, deployment-timeout.cli, to set the timout of the
application deployment of Wildfly. The timeout value is expressed in seconds
and it is defined by the new configuration property SERVER_STARTING_TIMEOUT
in the config.properties configuration file. If Silverpeas starting is too
long, with the default timeout of 5mn, the Silverpeas deployment can then
fail for timeout error. By setting this property with a greater value,
Silverpeas can take the time it needs to initialize all of its resources.

Aside that, in order to avoid the start/debug task of the installer to fail
when Silverpeas takes a long time to start, the configuration property
SERVER_STARTING_TIMEOUT is also used as timeout for JBoss to respond to the
tasks.

Author: mmoqui

src/main/dist/bin/build.gradle

@@ -67,7 +67,7 @@ silversetup {
 
     bundles {
       // used to construct the Silverpeas application from a descriptor of software components that
-      // made up Silverpeas
+      // made up Silverpeas. See silverpeas.gradle for software configuration.
       silverpeas = project.configurations.silverpeas
       tiers = project.configurations.library
     }
@@ -148,8 +148,9 @@ task start {
   description 'Starts Silverpeas'
   group 'Silverpeas'
   doLast {
+    long timeout = (project.silversetup.settings.SERVER_STARTING_TIMEOUT as Long) * 1000
     new JBossServer(project.silversetup.jbossHome.path)
-        .withStartingTimeout(project.silversetup.timeout.get())
+        .withStartingTimeout(timeout)
         .redirectOutputTo(project.ext.jbossOutputLog)
         .start()
   }
@@ -163,8 +164,9 @@ task debug {
   group 'Silverpeas'
   doLast {
     int port = (project.ext.has('port') ? project.ext.port as int:5005)
+    long timeout = (project.silversetup.settings.SERVER_STARTING_TIMEOUT as Long) * 1000
     new JBossServer(project.silversetup.jbossHome.path)
-        .withStartingTimeout(project.silversetup.timeout.get())
+        .withStartingTimeout(timeout)
         .redirectOutputTo(project.ext.jbossOutputLog)
         .debug(port)
   }
@@ -211,8 +213,9 @@ task reload {
   group 'Silverpeas Development'
   onlyIf { silversetup.installation.developmentMode }
   FileLogger log = FileLogger.getLogger('reload')
+  long timeout = (project.silversetup.settings.SERVER_STARTING_TIMEOUT as Long) * 1000
   JBossServer jboss = new JBossServer(project.silversetup.jbossHome.path)
-      .withStartingTimeout(project.silversetup.timeout.get())
+      .withStartingTimeout(timeout)
       .redirectOutputTo(project.ext.jbossOutputLog)
       .useLogger(log)
   doFirst {

src/main/dist/configuration/jboss/deployment-timeout.cli

@@ -0,0 +1,2 @@
+/system-property=jboss.as.management.blocking.timeout:add(value=${SERVER_STARTING_TIMEOUT})
+/subsystem=deployment-scanner/scanner=default:write-attribute(name=deployment-timeout,value=${SERVER_STARTING_TIMEOUT})

src/main/dist/configuration/sample_config.properties

@@ -81,6 +81,14 @@
 # false. By default false.
 #SERVER_SECURED=false
 
+# The timeout in seconds for the server to start Silverpeas. By default, the timeout of the
+# application deployment of the server (5mn in Wildfly). When Silverpeas is started by the server
+# (when it is deployed in the JEE jargon), it can take some times to initialize the resources that
+# depends on the amount of the data managed by Silverpeas and on the performance of both the
+# hardware and the filesystem. If you encounter a timeout error at Silverpeas starting, then
+# change the value here (for example, by setting it to 900 for 15mn)
+#SERVER_STARTING_TIMEOUT = 300
+
 ####################################################################################################
 ## Properties of the database to use for Silverpeas.
 ####################################################################################################