Some of our users are experiencing this type of error here.
Its not the first time i see such a problem. Does anyone know what could be causing it?
This seems related, unfortunately no solution listed but that doesn’t mean it doesn’t exist!
@chase.freeman well do you the error only appears on version 2.29 or it was fixed in the later versions?
You can restart your tomcat to see what happen.
Yes we restarted the server and everything went back to normal. Thanks