C
Chris LaJoie
Hi,
I have an app that runs many simultaneous threads. I have noticed (took me
a while to figure out what it was doing though) that sometimes if there is a
problem, the thread will simply terminate on the line that caused a simple
exception, but does not throw any error or inform me in any way. I recently
found one of these problems in a function that does an int.Parse(string),
however, there are many more. I was apparently wrong in assuming that
int.Parse would throw an exception if an invalid character was in the string
to be parsed. Instead it simply terminates the thread. I am very careful
with my error handling, and put it everywhere it is required, so that is not
the problem.
Another thread which is running simultaneously MUST wait for a signal from
the thread with the problem in order for it to continue. When it does not
recieve the signal, it continues in an infinite loop until I shut the
program down. This is a huge problem, because the application we are
developing is one that is required to continue operating even if there is a
problem such as this, as it will be running constantly on our server for
2000+ customers.
To clear up any confusion, I'm having a problem with a thread that is
terminating while in the middle of execution. I doubt there is a solution,
but does anyone know of a workaround? Thanks,
Chris LaJoie
I have an app that runs many simultaneous threads. I have noticed (took me
a while to figure out what it was doing though) that sometimes if there is a
problem, the thread will simply terminate on the line that caused a simple
exception, but does not throw any error or inform me in any way. I recently
found one of these problems in a function that does an int.Parse(string),
however, there are many more. I was apparently wrong in assuming that
int.Parse would throw an exception if an invalid character was in the string
to be parsed. Instead it simply terminates the thread. I am very careful
with my error handling, and put it everywhere it is required, so that is not
the problem.
Another thread which is running simultaneously MUST wait for a signal from
the thread with the problem in order for it to continue. When it does not
recieve the signal, it continues in an infinite loop until I shut the
program down. This is a huge problem, because the application we are
developing is one that is required to continue operating even if there is a
problem such as this, as it will be running constantly on our server for
2000+ customers.
To clear up any confusion, I'm having a problem with a thread that is
terminating while in the middle of execution. I doubt there is a solution,
but does anyone know of a workaround? Thanks,
Chris LaJoie