Please check the link here for similar functionality on version 8.x:
How to tune the number of connections in the server database pool
Prefer JNDI datasources to JDBC datasources
One potential bottleneck is a datasource that doesn't offer a connection pool. This is why we recommend using JNDI, which allows you to configure an entire connection pool that resides within the container. In Tomcat, this involves modifying the /jasperserver-pro/META-INF/context.xml file, and editing the object's values for the maxIdle and maxActive attributes.
References
- Documentation » JasperReports Server Administration Guide Beta
- Wiki » Connecting JasperReports Server to your Database » Acquire the Database Driver Package
- Wiki » How to Tune the number of connections in the server database pool.
- MariaDB Foundation » MariaDB Java Client (Drop-in replacement for MySQL, Java JDBC Driver distributed with JasperReports Server v5.5 on)
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now