VSE recorder throwing ERROR in DevTest Portal: Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext-Please choose a different port
search cancel

VSE recorder throwing ERROR in DevTest Portal: Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext-Please choose a different port

book

Article ID: 372590

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Trying to record a HTTPS VS  in DEVTEST Portal and getting the error "Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext. Please choose a different port" but able to record HTTP VS on the same port.

Verified VSE server and seen that there were no recordings in the Portal or any VS's deployed on that specific port.

Below is the exception seen in VSE log.


Exception: 
============================================================================
| Message: java.lang.NoClassDefFoundError: Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext
----------------------------------------------------------------------------
| Trapped Exception: Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext
| Trapped Message: java.lang.NoClassDefFoundError: Could not initialize class com.itko.lisa.utils.ssl.VSESSLContext  
Please choose a different port...

Environment

DEVTEST 10.7.x and up

Cause

By design the below properties are configured in DevTest_Home/lisa.properties file and uses webreckeys.ks and vse.ks from the DEVTEST folder.  

ssl.client.cert.path={{lisa.default.keystore}}
ssl.client.cert.pass=xxxxxxxxxxxxxxxxxxx

ssl.server.cert.path={{LISA_HOME}}vse.ks
ssl.server.cert.pass=xxxxxxxxx

lisa.default.keystore={{LISA_HOME}}webreckeys.ks
lisa.default.keystore.pass=xxxxxxxxxx

On the VSE Server, the keystore files webreckey.ks and vse.ks were missing from the DEVTEST install directory and  this caused the issue; as VSE Recorder is configured with the default file webreckeys.ks.

Resolution

Restore the keystore files webreckeys.ks and vse.ks to the DEVTEST install folder and Restart VSE. This should resolve the issue. 

If any specific keystore file is used in the VSE Recorder, make sure the file is available in the specific path on the server.