I have logger adapter configured to SQL Server 2000. Some times the integration component being logged throws exception and creates log entry. Exception contain huge call-stack and then it generates error in the logger adapter that the input data is large and that the data will be truncated. The problem is after this exception, the logger adapter stops working without giving any notification.
How to avoid huge call-stack stopping the logger adapter functionality?