Virtual Service error: ERROR com.itko.lisa.vse.stateful.ConversationalStep - An error occurred executing a conversational step.
search cancel

Virtual Service error: ERROR com.itko.lisa.vse.stateful.ConversationalStep - An error occurred executing a conversational step.

book

Article ID: 243096

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Virtualized a stub using Java protocol and java classes. After deploying the service in the portal and setting the execution mode as live system, the traffic is not going to the live system. VSI step in our stub is being triggered and not sure why this is happening. Below is an error found in the logs:

2022-06-01 21:03:25,564Z (17:03) [Java-ConnectionReset-NPE2 [VS_Java-ConnectionReset-NPE2_Run]/2] ERROR com.itko.lisa.vse.stateful.ConversationalStep - An error occurred executing a conversational step.

============================================================================
| Exception:
============================================================================
| Message: No request found in the lisa.vse.request test state property.
----------------------------------------------------------------------------
============================================================================

The service is built  after setting up a java recorder. No issues during recording and after that built a simple service. When deployed the same with live mode to validate the recorded use case, it's throwing lot of errors but surprisingly the use case also passed. Because of high volume of errors it does an auto shutdown of the service. Also noticed in the inspection view that even if the live mode is on it's still going to VS Image step and erroring out there itself.

Environment

Release : 10.6 and up

Component : DevTest Virtual Service

Cause

For Java virtualization, you cannot switch between Most Efficient mode and any VS mode that goes to the LIVE system. 

Resolution

The workaround is to first start the application so the agent will start properly then the Virtual Service can be started, so it will be in playback mode. Then you can make transactions against the Virtual Service and get valid response. If you want some calls to go to the LIVE system then you will need to customize your VSM.

Clean up on the VSE:

1. Bring down the VSE
2. Delete all the vse.log files.
3. Delete all the Virtual Services log files as well.
4. Start the VSE.

Refer to KB article: https://knowledge.broadcom.com/external/article?articleId=74737