That doesn't sounds right, but can you add the check to ErrorAction anyway?
On Thu, May 28, 2009 at 8:44 PM, Corey Kaylor <[email protected]> wrote: > It could be possible that if any consumer does something that causes the > transaction to be faulted i.e. an error in sql server and handles the > exception or if an error occurs in the message module for the same scenario > where the transaction is faulted but handled. There is potential that the > block below would have a null exception but fails to complete the > transaction, which would then lead to the ErrorAction throwing a null > reference exception in the call to exception.ToString(). Might be unrelated, > just thinking of possibilities. > > if (exception == null) > { > try > { > if (tx != null) > tx.Complete(); > return; > } > catch (Exception e) > { > logger.Warn("Failed to complete transaction, moving to > error mode", e); > > } > } > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
