Is Virtual Service Causing Read Timed Out Exception

[Legacy User]

We have a virtual service running in a performance virtual service environment.  When the team sends single requests to the virtual service, it functions as expected.  However, when doing performance testing, (high load) the client is throwing multiple of the following exceptions ::

 

java.net.SocketTimeoutException: Read timed out exception

 

I'm not seeing any errors on the DevTest Console and log files aren't showing any errors either.

 

Is there something else I can check to see if it is the Virtual Service that is causing the timeout exceptions?

[Surya Anil Kumar Suravarapu]

Hello Wallace,

 

         Try increasing the capacity of the virtual service and check if these socket timeout errors get resolved at application end. The issue may have been that the capacity allocated to the service is unable to process the number of incoming requests.

 

Thank You,

Surya.

[Legacy User]

Hello sursu06,

 

Thanks for the response.  When I attempt to update the capacity, I get the following error.

 

Any ideas?

[Surya Anil Kumar Suravarapu]

Hello Jeff,

 

          You need to have performance mode enabled for you to update the capacity to a higher value for the virtual service. Please confirm if the performance mode is enabled for the VSE.

 

Thank You,

Surya.

[Legacy User]

Hi sursu06,

   Would you happen to know how I can check to make sure performance mode is enabled?

[Prem Bairoliya]

Check the information provided in the link below

 

Tech Tips: "Error attempting to update the attributes for the VSE Service"

[Legacy User]

Prem_Bairoliya when I go to check the local.properties file, that setting doesn't even exist.  Is it 'normal' that I would have to create the setting and set it?

[Prem Bairoliya]

It is not present by default. Following has to be added to the local.properties used by the VirtualServiceEnvironment

 

lisa.vse.performance.enabled=true

[Legacy User]

Prem_Bairoliya Ok, I will give that a shot here in a second.  We are running the VSE via the VirtualServiceEnvironmentService found in {DEV_TEST_HOME}/bin.  Will I need to restart the service in order for the config change to take effect?

[Prem Bairoliya]

Yes, the service will need to be restarted for it to pickup the setting.

[Legacy User]

Ok.  In that case, I will have to try to do it later this evening.  We have multiple teams currently consuming services running in the VSE and I can't restart it at this time.  I will hopefully get a chance tonight to restart the VSE and will then update this thread with what I find.

[Legacy User]

Prem_Bairoliya and sursu06

I added the recommended configuration to my VSE's local.properties file, rebooted the VirtualServiceEnvironmentService and now I am able to increase the Concurrency Capacity. 

 

Hopefully this will get rid of the Time Outs that we were experiencing under load.

 

Now I just need to figure out how that configuration got removed.

 

Thanks for all of the help!

[Surya Anil Kumar Suravarapu]

Hello Jeff,

 

      Please see the link below for information on how to enable performance mode for the VSE. You should have performance server license to be able to do this.

 

SV Installation and Configuration - DevTest Solutions - 9.5 - CA Technologies Documentation

[Legacy User]

sursu06 we definitely have a performance server license for this VSE.  It's a controlled lab environment of ours that we only use for performance testing.  I'm going to try Prem_Bairoliya's suggestion of adjusting Think Scale and if that doesn't help, then  I will look at the performance mode settings.  Thanks for the help! 

[Prem Bairoliya]

I would try to stop/remove the service from the VSE.

From your screenshot it shows that you are using Think scale of 100% - To support performance needs, it is recommended to run with 0% think scale.

With a Capacity of 1 & think scale of 0, check what is the best throughput your virtual service is able to provide before increasing the capacity.

[Legacy User]

Prem_Bairoliya thanks for the responses!

I will try stoping/removing the service from the VSE, then redeploying and setting the think scale to 0% before I attempt to change concurrent capacity.  I will let you know how it goes.

[Legacy User]

Prem_Bairoliya unfortunately setting the Think Scale to 0% didn't prevent the time outs from occurring.  I will now checkout whether or not performance mode is setup.