We made a workaround similar to it: 1) Autorestart of our windows service in case of crash. 2) Remembering the hash of resume that crashed and do not convert it next time.
However that is only ok as an ugly patch, because our windows service runs many other processes in parallel to that document converter queue. All these processes are terminated in the middle.
Another problem is that web site will also crash. Fortunately IIS automatically recovers crashed thread, but still it makes me think that hard crashes like these can add instability to our system.
no subject
1) Autorestart of our windows service in case of crash.
2) Remembering the hash of resume that crashed and do not convert it next time.
However that is only ok as an ugly patch, because our windows service runs many other processes in parallel to that document converter queue.
All these processes are terminated in the middle.
Another problem is that web site will also crash.
Fortunately IIS automatically recovers crashed thread, but still it makes me think that hard crashes like these can add instability to our system.