#1 2019-02-01 10:13:56

phenaut
Member
From: FRANCE
Registered: 2017-10-30
Posts: 14

Pool never releases opened connections and finally crashs

Hello,

upgrading from 3.0.3 to 3.0.5, the MySQL server becomes unreachable after 1 or 2 hours :

I saw that Pool never releases connections and can't use the old ones anymore, when the MaxPoolSize is reached the server
doesn't establish new connections and if the are all 'burned' we can't establish new connection and need a tomcat reboot :

I tried to modify pool.cf like this :

<configuration>
   <pool>
      <defaultconfig>
         <maxPoolSize>40</maxPoolSize>
         <minPoolSize>5</minPoolSize>
         <initialPoolSize>5</initialPoolSize>
         <acquireRetryAttempts>10</acquireRetryAttempts>
         <acquireRetryDelay>500</acquireRetryDelay>
         <checkoutTimeout>10000</checkoutTimeout>
         <maxConnectionAge>1000</maxConnectionAge>
         <maxIdleTime>500</maxIdleTime>
        <maxIdleTimeExcessConnections>500</maxIdleTimeExcessConnections>
      </defaultconfig>
   </pool>
</configuration>

but the oldest idle connection has 3298 sec...

Any idea ?
Thanks for your support.

Last edited by phenaut (2019-06-18 11:44:48)

Offline

#2 2019-02-01 10:51:38

eduardo
Administrator
Registered: 2016-11-01
Posts: 1,327
Website

Re: Pool never releases opened connections and finally crashs

Hi phenaut,

is this the same issue discussed here?: https://forum.reportserver.net/viewtopic.php?id=1315
Please check if you can reproduce the issue as well stressing the refresh button in the dashboard as in the other thread. Is this the same behavior?

Regards,
Eduardo

Offline

#3 2019-02-01 12:52:38

phenaut
Member
From: FRANCE
Registered: 2017-10-30
Posts: 14

Re: Pool never releases opened connections and finally crashs

Hello Eduardo,
yes very similar ...

But some differences : between 3.0.3 and 3.0.5 the jasperreports-6.4.1.jar is the same.
By stressing the server I was able to crash with dynamic list or jasper report, as well.

Some connections are cleared from the pool, I don't know yet why it's able to clear someone and not others ones ...
may be linked with the nature or the request ? (Jasper on Dynamic ?)

Thanks for yor help...
I will use also a workaround with big pool and night reboot to wait the patch !

Last edited by phenaut (2019-02-01 12:53:35)

Offline

#4 2019-02-04 11:38:53

phenaut
Member
From: FRANCE
Registered: 2017-10-30
Posts: 14

Re: Pool never releases opened connections and finally crashs

Hello Eduardo
the connections made by the Dynamic Lists are released, not them made by Jasper ... So this confirm the same behaviour with topic #1315..

I added a crontab with /etc/init.d/bitnami restart to clear pending connections ...

Is it possible to restart 'less' processes by just restarting the pool process involved in MySQL connection ?

thanks a lot for your support.

Last edited by phenaut (2019-02-05 08:12:32)

Offline

Board footer

Powered by FluxBB