i'm experiencing the described behaviour with 4.1.5.SP1. was this issue fixed for that branch or i have to patch it by myself?