org.mapdb.DBException$DataCorruption: wrong header in file: DEVTEST_HOME\vsBuilderSessions\VSE_2013\session_keys.vsk (OR) Unexpected exception during startup. com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException
search cancel

org.mapdb.DBException$DataCorruption: wrong header in file: DEVTEST_HOME\vsBuilderSessions\VSE_2013\session_keys.vsk (OR) Unexpected exception during startup. com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException

book

Article ID: 136919

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

VSE Service fails to stay running on Production server, and throws the following error:

ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Unexpected exception during startup.
com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException

(OR)
 
2019-09-06 12:13:58,044Z (08:13) [main] ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Unexpected exception during startup.
org.mapdb.DBException$DataCorruption: wrong header in file: C:\CA\DevTest\vsBuilderSessions\VSE_2013\session_keys.vsk
 
Actions taken:
All DevTest Services stopped
Contents of lisatmp folder deleted
Server restarted with automatic start on the DevTest Services
Contents of lisatmp folder copied, zipped, and will be uploaded
Contents of vsBuilderSession folder copied, zipped, and will be uploaded
 

Environment

All supported DevTest releases.

 

Cause

This error happens when files in the vsBuilderSessions/VSE_2013 or vseRecording\VSE_2013 get corrupted. 

The vsBuilderSessions creates bundles when you create Virtual Services from the Portal. These bundle contain resources needed for this Virtual Service, for example a WSDL files or RR pairs. There are cached names for these bundles in the vsBuilderSessions catalog. If files are damaged, deleted or changed, the VSE cannot load it, and as a result it throws the error.  They get corrupted if there is an interruption during the recording, like for example a bad endpoint. 

The vseRecording is used when recording a Virtual Service using DevTest Portal, the raw traffic is created in this folder. 

Resolution

Needed to rename these folders and restart the VSE and it came up with no issues:

 

1. DEVTEST_HOME\vsBuilderSessions\VSE_2013

2. DEVTEST_HOME\vseRecording\VSE_2013

3. Delete the mar.tracking files in the DEVTEST_HOME\vseDeploy\VSE_2013 folder
4. Deleted all the logs files.
5. Started VSE service.