Refer title for the bug. This seems to have been introduced after 1.2.0.Final because in that version we didn't have this problem. Failure happens in 1.7.0.Final. Checked the logs and there's a NullPointerException thrown.