This is a bug in version 4.1.9 and it's fixed from version 4.3.0beta and beyond.
Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.
You have a different solution? A short tip here would help you and many other users who saw this issue last week.