Configure Maximum Simultaneous Deployments
Here's how to configure max.simultaneous.deployments in MidVision's Application Release Automation tool in the rapiddeploy.properties file. Please see the section below:
max.simultaneous.deployments=5
By default this setting is set to 5 in the rapiddeploy_default.properties file and this setting can be overwritten in the rapiddeploy.properties file. This property indicates how many jobs the RapidDeploy framework server will concurrently run at any one time. If this limit is reached then new jobs will queued until one of the running jobs completes and the first job in the queue will be started. Each job spawns a new thread to monitor the job progress and log output, which is displayed in the UI and also saved to the project log location. This setting can be increased or reduced depending on the memory resource available on your server. If the value is changed then the RapidDeploy framework server needs to be restarted for this setting to take effect.
Threads
Since each concurrent deployment adds multiple threads (for logging, monitoring etc), please ensure that you also increase appropriately the number of threads available in your web container. Normally this will be the web Container thread pool max threads setting.
For the Tomcat web container, this can be set in the server.xml, on the connector as follows:
<Connector connectionTimeout="20000" port="8087" protocol="HTTP/1.1" redirectPort="8443"
maxPostSize="0" maxThreads="200"/>