LabVIEW crahses when waiting for TCPIP Connection

[A_Senthilnathan]

I am developing a server client application in LabVIEW. The server module creates Listener and waits till the client is connected to it. Once the client is connected server transmits the data. There are two clients in my application. The same data has to be transfered to these clients. These clients may connect / disconnect at any time. There are dedicated ports for each client.

LabVIEW crashes when one of the client is not up and running. That is when one client is connected to it. at this time the server waits for the another client to connect in a seperate loop.

LabVIEW doesnot crash if the listener for the second port is not created. (as if there is only one client).

Why is labVIEW crashes when it creates and
waits for a TCP IP connection. I am runnning the server and client software in the same PC.

Thanks,
A. Senthilnathan.

[Mads]

I've had a mysterious problem earlier where the read would occationally crash LabVIEW if it had a timeout input of 2ms, changing the timeout to something else removed the bug(!).

Not an answer to your question, but why are you using two different ports? If you are going to have multiple clients you can still use one and the same port (just as web servers use port 80). If the clients are very different it might be practical (although not necessary), but if they are one and the same there is no need for using different ports.

If you have an example of the code you can share it may be easier to spot the problem.