In our system, this issue appeared when @EntityListeners was added to one single entity (no other entities had it before this). Perhaps this could help in finding the problem.