Why are my executions defintions failing to connect to my Lab Manager execution server?
In the past configurations were
captured "statefull" on the Lab Manager side, which means
that the VM image was captured during normal service (i.e. with the
O/S running). When such a configuration is deployed for a second
time, the memory containing the running OS is loaded and the VM is
loaded and runs in a much shorter time than the time required for
the initial deployment.
To improve performance of checkout and deployment, configurations
are now captured "stateless", which means that the O/S in
the VM image is shut down and needs to be re-started each time the
configuration is deployed again.
Obviously, this causes the timing of the deployment to change and
this may result in a problem with stateless captured configurations
to provide the execution server connection in time (because the O/S
has to be turned-on and started-up). Consequently, the execution
may fail in TestManager if the execution server cannot be connected
in time.
This can be avoided by increasing the value in the following
setting in the SCCAppServerBootConf.xml file:
120
Increasing this value will support statefull as well as stateless
capturing, but the downside is that in any error situation more
time will pass until the error is recognized.
Support
Documentation
Learning Services
Partner Programs