...
Our current report generation design has a problem dealing with concurrent users concurrently generating the same report for the same enterprise. Deadlock on the database may happen occurr due to the way we keep the information isolated to from users from of other enterprises.
In case If this happen happens, a warning from JasperServer will pop up to the end user, user . They should generate the report again and unless another user asked for the same report again, it will be generated without problem.
...
You can configure the slave server to avoid this problem by tweaking the innodb concurrency settings.
Set this In your my.cnf config file, set these two global innodb parameters:
| Code Block |
|---|
innodb_thread_concurrency=1 innodb_concurrency_tickets=50000000 |
In your my.cnf config file to This will ensure innodb will serialize reports, avoiding the deadlock error popping out to popup for the end user