"Did you find out the issue here ?" Yes, I believe so and why I am here...
While we do have a listener for the messages so I do see them, but it was not made to look for these messages and do much with this specific condition (we use it to monitor IO and other perf stats). We assumed that all "bad things" in terms of "attempts to modify the database not succeeding" would be throwing exceptions (silly me).
That is, I see the messages and can certainly add my own "throw," but since AseException is internal, I cannot convert them into what they "should be" in my code.