VSE has shut down with java.lang.OutOfMemoryError error in the vse.log

Products

• CA Application Test
• CA Continuous Application Insight (PathFinder)
• Service Virtualization

Issue/Introduction

VSE shut down abruptly. VSE.log file has shown the below error:

 

FATAL com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Unexpected exception during startup.

java.lang.OutOfMemoryError: unable to create new native thread

                at java.lang.Thread.start0(Native Method)

                at java.lang.Thread.start(Unknown Source)

                at java.util.Timer.<init>(Unknown Source)

                at com.itko.lisa.coordinator.CoordinatorImpl.startTest(CoordinatorImpl.java:594)

                at com.itko.lisa.coordinator.VirtualServiceCoordinator.startTest(VirtualServiceCoordinator.java:658)

                at com.itko.lisa.coordinator.VirtualServiceImpl.start(VirtualServiceImpl.java:1037)

                at com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.startTheService(VirtualServiceEnvironmentImpl.java:1497)

                at com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.loadInitialServices(VirtualServiceEnvironmentImpl.java:550)

                at com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.main(VirtualServiceEnvironmentImpl.java:347)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

                at java.lang.reflect.Method.invoke(Unknown Source)

                at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

                at com.install4j.runtime.launcher.Launcher.main(Unknown Source)

 

Environment

All supported DevTest releases.

Cause

VSE has run Out of Memory. The memory allocation to this application is not sufficient for the kind of load it is handling at the moment.

Memory and ulimit resources too low.

Resolution

Increase the memory by -Xms and -Xmx values in the VSE’s vmoptions file i.e. VirtualServiceEnvironment.vmoptions  [Or VirtualServiceEnvironmentService.vmoptions if running the VSE as a service].

Example of such setting in the vmoptions file is [Ensure there are given in two different lines]:

 

-Xms512m

-Xmx2g

 

Also need to make sure the ulimit for "open files" and "max user processes" are set to 30000, this is what we recommend.  Make sure the Linux admin sets these values for both hard and soft limits.