LabVIEW crash or hang | When LabVIEW service didn't respond back to the LabVIEW client

[navinsubramani]

When a LabVIEW client API is called to LabVIEW service which doesn't have the response method called. Then,

1. The LabVIEW client gets hung and waits infinitely for the LabVIEW service to respond.

So, I notice that's the mistake in the LabVIEW service for missing the implementation of the response method. Maybe should it timeout at client's end? Either way, I go to server and click stop to stop the service.

2. LabVIEW service gets hung in the "Stop Server" VI. and client also was hung on the method.

3. So, I abort the client VI and it aborts properly. But the server VI couldn't be aborted.

4. So, I had to close the project to escape and I get stuck with this.

5. Kill LabVIEW from task manager.

[BShermanator]

Aside from ensuring a Set Response method is always called in the server, I created a wrapper class to abstract my application from the autogenerated code. The same behavior described above happens if there is an error on the input of the set response VIs. I want to ensure I always send a response.