Virtual Service Environments (VSEs) shut down intermittently (e.g., weekly) even though the underlying Windows or Linux service appears to be running. The services may drop from the DevTest Portal or Registry unexpectedly.
The Virtual Service Model (VSM) contains a hardcoded or absolute path to a keystore (e.g., C:/DevTest/<keystore>.ks). If the VSE service cannot access this path during runtime or after a registry re-sync, the VSM fails, which can trigger a shutdown of the virtual services within that environment.
Symptoms include:
To resolve this, update the VSM to use property-based relative paths to ensure the keystore is always accessible to the DevTest components.
C:/DevTest/vse2048.ks{{LISA_HOME}}/vse2048.ks or {{LISA_PROJECT_ROOT}}/Data/vse2048.ks..mar archive to the VSE.vse2048.ks file into your DevTest Project folder (e.g., inside the /Data directory)..mar archive and available wherever the service is deployed.