Maybe this is the answer.
I had similar issue few months ago and it looks like the exception is consumed and handled on other layer.