One of my queues calls a third-party assembly that was written in unmanaged code. We cannot control this code, but everyone so often it'll cause a Corrupted State Exception (specifically an AccessViolationException). Since these exceptions cannot be caught, RSB will fail without moving the message to the error subqueue. This is a problem as the message will still remain in the queue, when RSB starts back up again it'll repeat the cycle ad infinitum.
Right now, I have an additional service which monitors my queues. If a service fails to start after three times, it assumes there's a fatal message that cannot be processed and it'll backup and then purge the messages in that queue. This works, but I was wondering if there was a more elegant way to be processing these messages? -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
