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