JBoss as7: timeout deploying JBoss applications

Symptom: During JBoss startup and deployment, due to software package problems, the deployment time exceeds the default JBoss time (60 seconds). JBoss redeployment interrupts the previous deployment. This repetition causes the website to fail to start.   Code: KB-E1037 Issue:

There is an error message in log file while deploying JBoss Application

Error [Org. JBoss. as. server. deployment. deployment] (deploymenttransfer-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.

Resolution:

In the local git repository of the application locate File ". openshift/config/stanalone. xml" and open it in an editor.

Look up this section

<Subsystem xmlns ="URN: JBoss: domain: deployment-Timeout: 1.0"> <Deployment-deployment scan-interval ="5000"Relative-To ="JBoss. server. Base. dir"Path ="Deployments"/> </Subsystem>
 

And add "deployment-Timeout" attribute to the "deployment-Timeout" tag with big enough number. E. g.

<Subsystem xmlns ="URN: JBoss: domain: deployment-Timeout: 1.0"> <Deployment-deployment scan-interval ="5000"Relative-To ="JBoss. server. Base. dir"Path ="Deployments" Deployment-Timeout = "1200"/> </Subsystem>
 

 
The attributes are
 

Name	Type	Description
Name	String	The name of the queue.DefaultIs used if not specified
Path	String	The actual filesystem path to be scanned. treated as an absolute path, unless the 'relative-to 'attribute is specified, in which case the value is treated as relative to that path.
Relative-	String	Reference to a filesystem path defined in the "paths" section of the server configuration, or one of the System Properties specified on startup. In the example aboveJBoss. server. Base. dirResolves {{$ Jboss_home/Standalone
Scan-Enabled	Boolean	If true scanning is enabled
Scan-interval	Int	Periodic interval, in milliseconds, at which the repository shoshould be scanned for changes. A value of less than 1 indicates the repository shoshould only be scanned at initial startup.
Auto-deploy-zipped	Boolean	Controls whether zipped deployment content shocould be automatically deployed by the specified without requiring the user to add a. dodeploy marker file.
Auto-deploy-exploded	Boolean	Controls whether zipped deployment content shocould be automatically deployed by the specified without requiring the user to add. dodeploy marker file. setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content.
Deployment-Timeout	Long	Imeout,In seconds, A deployment is allows to execute before being canceled. The default is 60 seconds.

Refer:

Https://openshift.redhat.com/community/kb/kb-e1037-timeout-deploying-jboss-applications

https://docs.jboss.org/author/display/AS7/Deployment+Scanner+configuration