Virtual services start/stop API endpoint throws NullPointerException

Products

• Service Virtualization

Issue/Introduction

When using the API endpoints provided by CA LISA Invoke 2.0  to manage virtual services start/stop, update, change executionMode/thinkScale, virtual services crashing and throwing the below response:

{

    "id": 1007,

    "addInfo": "\njava.lang.NullPointerException\n\tat com.itko.lisa.coordinator.VirtualServiceCoordinator.ensureProjectTree(VirtualServiceCoordinator.java:656)\n\tat com.itko.lisa.coordinator.VirtualServiceImpl.start(VirtualServiceImpl.java:1063)\n\tat com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.startTheService(VirtualServiceEnvironmentImpl.java:1472)\n\tat com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.startService(VirtualServiceEnvironmentImpl.java:1438)\n\tat sun.reflect.GeneratedMethodAccessor396.invoke(Unknown Source)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:498)\n\tat com.itko.lisa.net.RemoteMethodExec.execute(RemoteMethodExec.java:57)\n\tat com.itko.lisa.net.ServerRequestHandler.processRMIMessage(ServerRequestHandler.java:533)\n\tat com.itko.lisa.net.ServerRequestHandler.access$600(ServerRequestHandler.java:70)\n\tat com.itko.lisa.net.ServerRequestHandler$5.run(ServerRequestHandler.java:451)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\n\tat java.lang.Thread.run(Thread.java:745)\n\n"

}

Using the following API: http://sRegistryHostname:1505/api/Dcm with the following methods and end points :

Environment

Release : 10.x

Component : CA Service Virtualization

Cause

Intermittent issue when MAR file is not available

Resolution

The intermittent failures are happening mainly due to MAR access problem. When the MAR is not available the reported exceptions happen.

Below are the VS status codes and what it means.

0 - Virtual Service is loaded

1 - Virtual Service is starting

2 - Virtual Service is running

3 - Virtual Service is stopping

4 - Virtual Service is ended.