Virtual Service Model ended running after 3 errors
search cancel

Virtual Service Model ended running after 3 errors

book

Article ID: 38127

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

We have noticed that the VS shuts down after 3 consecutive errors. How can we change this behavior?


We would like to have the Virtual service restart automatically. Is there a way to do this?

Environment

All supported DevTest releases and plaforms.

 

Cause

By default, a Virtual Service will go offline after 3 consecutive errors

Resolution

By default, the VSE will shut down after 3 consecutive errors are seen. There's a property, which can be added to the local.properties file, to change this behavior.

The 'lisa.vse.max.hard.errors' property allows you to configure the number of consecutive errors allowed before the VSE service shuts itself down. 

To modify the default behavior, open the local.properties file on the VSE server, and add the property:

lisa.vse.max.hard.errors=<number>

Where <number> represents the number of allowed consecutive errors. The value can be 0 or greater.

    • A value of 0 means that no errors are allowed, and the service shuts down after the first error is seen.
    • To designate an unlimited number of errors, enter any negative number (-1).( This is NOT RECOMENDED)

For example: lisa.vse.max.hard.errors=100


After adding this property to your local.properties file on the VSE server, you will need to restart your server.

NOTE:
When setting lisa.vse.max.hard.errors to 100 or more you will also need to set the following:
lisa.coord.failure.list.size=10

If the above is not set you can run into Java heap Memory issues and the VS will through 1000s of errors...

Additional Information

Use the monitor feature to enable Auto restart:  Refer to documentation section "Monitor Virtual Services" of the release you are running for more information.