none
How to release database connections in Pentaho BI server?? RRS feed

  • Question

  • I am using Pentaho-BI server installation in my web application as a third party installation.I am using its saiku analytics and reporting files by embedding their specific links in iframe of my application. Problem is I am not getting how it creates database connections, in terms of numbers?? Because many times it throws error regarding 'No connection is available in pool'. I know there are properties like max available connection, max idle connections , wait and sql validation. But How to release connections?? And if Pentaho handles it in its own way then how?? Because increasing number of max connections available will create load on database server, when many users are using my BI server.

    One solution I found is just to restart my BI server, but It's not a valid solution for production environment. Other solution I think is scheduler, but I have no clues about it and not getting proper info on net.

    • Moved by Bob Beauchemin Sunday, November 23, 2014 7:02 PM Moved to the appropriate forum for client-side provider issues.
    Sunday, November 23, 2014 7:16 AM

Answers

  • The error message No connection is available in pool indicates a poorly written application that opens connections but do not close them appropriately. And more importantly do not explicitly dispose them but wait for garbage collection to take care of them.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Sunday, November 23, 2014 10:35 AM
  • The defaults for max connections are incredibly low. This is standard tomcat connection pooling stuff, I would definitely try increasing the default, see if that helps. you can monitor concurrent connections on the db side - just because you have 100 connections to the db it doesn't necessarily mean they'll be all used at once.

    Also; Are you using mysql? You should try the c3po pooling driver it handles timeouts and things better than the standard driver so you shouldnt ever get dead connections sitting in the pool.

    Monday, November 24, 2014 12:09 AM

All replies

  • The error message No connection is available in pool indicates a poorly written application that opens connections but do not close them appropriately. And more importantly do not explicitly dispose them but wait for garbage collection to take care of them.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Sunday, November 23, 2014 10:35 AM
  • The defaults for max connections are incredibly low. This is standard tomcat connection pooling stuff, I would definitely try increasing the default, see if that helps. you can monitor concurrent connections on the db side - just because you have 100 connections to the db it doesn't necessarily mean they'll be all used at once.

    Also; Are you using mysql? You should try the c3po pooling driver it handles timeouts and things better than the standard driver so you shouldnt ever get dead connections sitting in the pool.

    Monday, November 24, 2014 12:09 AM