VSE service shuts down intermittently due to inaccessible keystore path
search cancel

VSE service shuts down intermittently due to inaccessible keystore path

book

Article ID: 441098

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

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.

Environment

  • All supported DevTest releases.
  • Virtual Service Models (VSMs) configured with SSL/HTTPS using a local keystore path.

Cause

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:

  • VSE instances disappear from the DevTest Console/Portal.
  • The vse.log may show errors such as:
    • ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Unable to re-acquire DevTest Registry
    • com.itko.jms.IllegalStateException: The Session is closed
    • Errors related to finding or reading the <keystore>.ks file.

Resolution

To resolve this, update the VSM to use property-based relative paths to ensure the keystore is always accessible to the DevTest components.

Option 1: Map the Keystore with LISA_HOME Variables (Recommended)

  1. Open your Virtual Service Model (VSM) in the DevTest Workstation.
  2. Locate the Listen Step or Live Invocation Step.
  3. Update the Keystore file path to use property notation:
    • Change from: C:/DevTest/vse2048.ks
    • To: {{LISA_HOME}}/vse2048.ks or {{LISA_PROJECT_ROOT}}/Data/vse2048.ks.
  4. Save the VSM and re-deploy the .mar archive to the VSE.

Option 2: Move the Keystore to the Project Folder

  1. Copy the vse2048.ks file into your DevTest Project folder (e.g., inside the /Data directory).
  2. Update the path in your VSM to point to this new relative path.
  3. Re-deploy the virtual service. This ensures the keystore is properly bundled within the .mar archive and available wherever the service is deployed.

Additional Information