Multithreading causing Reader collision errors - Solution Options Requested

See more:

VB

multi-threading

I have an application that is doing reads from an OPC Server at a rate of one every tenth of a second with each read being in its own thread. It then creates a thread to write that information into the database.

Overall this seems to work fine but when I stop the process and try and restart it again a short time later, I get a lot of errors trying to write to the database which seem to suggest that the SqlReader is busy and hasn't been closed.

So I'm wondering what the solution options might be?

One thought I had was to create a thread that sat and slept until it was triggered to wake and write information to the database and then go back to sleep. This would seem to be a good option but would require that I understand how to actually trigger threads to wake up as well as handling the shutting down of the thread when the application is trying to close (which I currently have never done).

Part of me is wondering if I need to be putting monitor controls around my SQL connection to ensure that it closes the read before releasing the variable to other processes ... that perhaps that is the source of my problems.

I'm not sure what other options there might be so I would appreciate any thoughts or comments.

Thanks in advance.