05-15-2018, 10:16 PM
It sounds like you have a resource issue, or threads that are colliding. You are supporting multiple sessions that will access the thread you created. Are you accessing any tables or global variables? If so, you will need critical sections to prevent multiple threads from using that code at the same time. Or you have to create dynamic resources inside the thread execution code. Are you using a timer inside the thread? That too would require critical section support for multiple sessions.
This may be a case where you create a Service for the thread that you can communicate with from the user sessions. I use this setup for anything that requires external processing, or that needs high performance. I typically use a table with a status field to trigger the service. When the service has completed its work it can set the status to completed. The client just waits in a timer loop for the status to change. You can even report interim status updates if needed. That setup also scales extremely well.
This may be a case where you create a Service for the thread that you can communicate with from the user sessions. I use this setup for anything that requires external processing, or that needs high performance. I typically use a table with a status field to trigger the service. When the service has completed its work it can set the status to completed. The client just waits in a timer loop for the status to change. You can even report interim status updates if needed. That setup also scales extremely well.