Case Study: Getting QueryExecutionTimeoutException and LockTimeoutException when running report in JRS 7.5.2

Our user reported that their JasperReports Server (JRS)  7.5.2 in production suddenly had problems running reports with timeout issues relating to QueryExecutionTimeoutException and LockTimeoutExceptionthe. The reports were deployed years ago and they did not have this problem at all until a few days ago. The only change made to the JRS deployment was to add a new JNDI connection to the server (in context.xml). And there's no report DB changes (configuration or data volume) as far as the users know. All of a sudden, they got report execution problems with almost all their reports using this DB. Restarting this 8 node server farm did not help to fix anything and the problem persists.

The users have problems running certain reports but not the others. Occasionally, the problematic report runs without the error. Running reports by different users can sometimes work but there's no clear pattern on the circumstances that a report will/won't run.

After reviewing the server log files on all server nodes, Tech Support suspected the problem was with users' report database and have asked users to check with their DBA on MS SQL report DB to see if there's any errors in the log and suggested restarting the DB to see if it'll help. 

As it turned out, the issue is with a throughput limitation on users' database servers. "The DBA team increased the throughput and we are now seeing Jaspersoft running much better."

===========================================

TTC-20220224-2086387