Announcement

Migration of this forum

Dear users of this forum,

we are pleased to inform you that we will be updating the software behind this forum in the near future.

Existing posts, users and categories will remain untouched.

Important:

  • Each user will need to reset their password.
  • Please select "I forgot my password".
  • Enter the email address you used to register in this forum.
  • You will receive an email with a link to set a new password.
  • Please choose a new (secure) password and confirm the process.

We will keep you informed in the pinned thread.

Kind regards,
Your ReportServer Team


Migration des Forums

Liebe Nutzer dieses Forums,

wir freuen uns, euch mitteilen zu können, dass wir in naher Zukunft die Software hinter diesem Forum aktualisieren werden.

Existierende Beiträge, Nutzer und Kategorien bleiben weiterhin bestehen!

Wichtig:

  • Jeder Nutzer muss sein Passwort neu vergeben.
  • Wählt dazu einfach "Ich habe mein Passwort vergessen".
  • Gebt die E-Mail-Adresse ein, mit der ihr registriert seid.
  • Ihr erhaltet eine E-Mail mit einem Link zur Passwortvergabe.
  • Bitte wählt ein neues (sicheres) Passwort und bestätigt den Vorgang.

Wir halten euch im angepinnten Beitrag auf dem Laufenden!

Mit vielen Grüßen
Euer ReportServer Team

#1 2018-08-28 11:05:32

johncook
Member
Registered: 2018-08-28

Database connection timeout parameter

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

#2 2018-08-28 14:50:48

jalbrecht
Administrator
Registered: 2016-10-21

Re: Database connection timeout parameter

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

Board footer

Powered by FluxBB