I've implemented an acceptor service using QuickFIX/n, and it seems like whenever any type of error, like a malformed incoming message or bad sequence numbers, occurs, QuickFIX/n hides the message and deals with the error internally.
Is there a way of programmatically detecting these errors without having to look in the logs?