Hi Heintz,
It’s too bad to hear that you are getting these stack traces after updating. Would it be possible for you to enable JRebel Logging and send us a jrebel.log after recreating this problem? Steps on how to configure JRebel Logging can be found here:
https://zeroturnaround.com/software/jrebel/learn/sending-log/
The log can be sent to our support team at support@zeroturnaround.com. Is there any pattern you have observed for when this error occurs? Like is it only happening after making a particular type of change or only after changing a specific class?
Colton
