Michail Nikolaev your error seems different, and looks similar to another issue we fixed already. Could you verify it by trying 4.3.0.Final ? If it doens't work, please report a separate issue and possibly with a test to reproduce it.