Currently, if we hit the rest endpoint for running a report (/rest_v2/reports/path_to_report?format=CSV&displayType=CSV&etc.) and for some reason the report cannot be compiled, the server will respond with a message such as this: "There was an error on the server. Try again or contact site administrators. (Error UID: 3d862a3a-c638-4806-aa4c-727d1d595613)" Now, consulting google, everyone refers people to the jasperserver log, which is located in our tomcat deploy path: /usr/share/tomcat/webapps/ROOT/WEB-INF/logs/jasperserver.log However, the only thing logged there is this: "2021-02-17T15:06:40,483 ERROR SecureExceptionHandlerImpl,pool-9-thread-2383:116 - There was an error on the server. Try again or contact site administrators. (Error UID: 3d862a3a-c638-4806-aa4c-727d1d595613)" Obviously not very helpful. Is the lack of detail a symptom of logging level on some specific class that handles these exceptions? We had been using JasperReports Server 6.3.0 for years and this log always contained detail indicating what the issue was, i.e. bad sql, connection issue, whatever. Now the logs contain none of that detail and you are essentially left to guess what might be wrong, which is a long and arduous troubleshooting process that sometimes just results in no solution if you are unable to guess the actual underlying issue. What can be done to get the details of these errors?
