MSMQ Poison Messages

I have a problem when my transactional notification is not able to transport the message to my service it will do a rollback and try again. This is ok but how do I control that behavior and stop this transaction before it fills up my database with error logs. I would like to get hold of the message property current abort count and be able to shot down this queue connection when it reach, let’s say 100 retries.

What happened was that my notification tried for over 1 000 000 times to process this particular message and caused a lot of DB and IS problems.