PostgreSQL exceptions after time

Google Groups archive
1

I posted this on bitbucket but it seems the issues there ain’t read:

https://bitbucket.org/sjodogne/orthanc/issues/15/postgresql-exceptions-after-time

2

Hello,

Be sure that the bugs reported in the official bug tracker are read, but it takes time to take them into consideration by the development team.

Please also read the following recent announcement:
https://groups.google.com/d/msg/orthanc-users/Ss-O1Nfvw2I/jfkIQbCzGAAJ

My first impression after reading your report is that this issue is not related to Orthanc, but rather to an inappropriate configuration of your PostgreSQL server. Check for instance this discussion:
http://dba.stackexchange.com/questions/97534/is-there-a-timeout-option-for-remote-access-to-postgresql-database

Maybe someone in this discussion group has better knowledge of the system administration of PostgreSQL than me, and could give initial directions to help and resolve your problem.

Sébastien-

3

As it turns out that was exactly what the problem is, enabled the keep alive every 120 seconds and now it works great.

4

Fine! Thanks for the feedback. Great to know your problem is now solved.

The issue is now closed:
https://bitbucket.org/sjodogne/orthanc/issues/15/

I will add a notice on the Web site of the PostgreSQL plugin when I have time.