Error subqueue and Corrupted State Exceptions
10 views
Skip to first unread message
gs
Apr 24, 2012, 3:15:09 PM4/24/12
to Rhino Tools Dev
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?
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?
nightwatch77
Apr 26, 2012, 7:34:12 AM4/26/12
to rhino-t...@googlegroups.com
Move the faulting assembly to an external process and launch it from your RSB application?
Reply all
Reply to author
Forward
0 new messages