You are not logged in.
Pages: 1
Hi, I'm trying to setup high-available configuration for ReportServer.
With frontend part(which is located behind AWS ALB) there are no any issues - I've adjusted settings in java.security settings file to networkaddress.cache.ttl=5 and networkaddress.cache.negative.ttl=5
And that was enough to handle switch between two tomcat instances.
For database I'm using AWS RDS Postgres and during manual failover report server page hanged. And the only way to restore it's functionality - it is to close reportserver page and open again. Is it possible to fix this behavior?
I think it might be another cache parameter, but I don't know where. Hope you can help me
Thanks
Offline
Hi John.
for a start: did you check https://reportserver.net/en/guides/conf … tasources/ and here 4.1.2. Configuring the Connection Pool ?
By default, ReportServer will pool connections to relational database systems. This increases the stability of the system, since you can define an upper limit of simultaneously open connections and, furthermore, it improves the performance at the same time since database connections are kept open and ready for use. The connection pools can be configured both globally and per datasource. The configuration is done in the file /fileserver/etc/datasources/pool.cf. ...
...
<defaultconfig>
<maxPoolSize>40</maxPoolSize>
<initialPoolSize>10</initialPoolSize>
<acquireRetryAttempts>10</acquireRetryAttempts>
<acquireRetryDelay>500</acquireRetryDelay>
<checkoutTimeout>60000</checkoutTimeout>
<maxConnectionAge>7200</maxConnectionAge>
<maxIdleTime>3600</maxIdleTime>
</defaultconfig>
<pool16>
<acquireRetryAttempts>20</acquireRetryAttempts>
</pool16>
...
Pls. check further Details in the documentation.
hope this helps
wbr jan
Offline
Pages: 1