Jasper concurrency

Owned by Former user (Deleted)
Last updated: Jun 26, 2014 by MS (Unlicensed)Version comment

Issue detail

Our current report generation design has a problem dealing with users concurrently generating the same report for the same enterprise. Deadlock on the database may occurr due to the way we keep the information isolated from users of other enterprises.

If this happens, a warning from JasperServer will pop up to the end user. They should generate the report again and unless another user asked for the same report again, it will be generated without problem.

Workaround

You can configure the slave server to avoid this problem by tweaking the innodb concurrency settings.

In your my.cnf config file, set these two global innodb parameters:

innodb_thread_concurrency=1
innodb_concurrency_tickets=50000000

This will ensure innodb will serialize reports, avoiding the deadlock error popup for the end user

Unable to render {include} The included page could not be found.