Message-ID: <1659842433.2461.1432371966010.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2460_507214030.1432371966009" ------=_Part_2460_507214030.1432371966009 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Cargo has a timeout for container start and stop operations. If the time= taken to start/stop a container exceeds the timeout period the operations = is considered failed and the container is then set in the unknown state.
The default timeout value is 2 minutes (120000 milliseconds). This value= can be modified as shown below.=20 =20 =20
If you set the timeout to
0, CARGO will not wait for t=
he container to start or stop.
Shutdown usually takes much much shorther than startup, it therefore oft=
en makes sense to use a shorter timeout for stopping the container than for=
starting it. With the Cargo Maven2 plugin, this is easy to do: indeed, in =
<execution> block of the Maven2 plugin, you can hav=
<configuration> blocks. When done so, the pl=
ugin will use an inheritance scheme; i.e. for each execution the outermost =
configuration elements will be overriden by innermost elements each time th=
ese are defined.
Here is an example that uses different timeouts when starting and stoppi= ng the container: