# PostgreSQL exceptions after time

**URL:** <https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358>\
**Category:** Google Groups archive\
**Created:** [February 22, 2016, 9:31am UTC](https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358 "2016-02-22T09:31:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Toshko\_Andreev](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/t/3ec8ea/32.png) [@Toshko\_Andreev](https://discourse.orthanc-server.org/u/Toshko_Andreev)\
**Post date:** [February 22, 2016, 9:31am UTC](https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358/1 "2016-02-22T09:31:01Z")

</div>

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](https://bitbucket.org/sjodogne/orthanc/issues/15/postgresql-exceptions-after-time)

---

<div class="post-metadata">

**Author:** ![jodogne](https://discourse.orthanc-server.org/user_avatar/discourse.orthanc-server.org/jodogne/32/1511_2.png) [@jodogne](https://discourse.orthanc-server.org/u/jodogne)\
**Post date:** [February 22, 2016, 9:39am UTC](https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358/2 "2016-02-22T09:39:28Z")

</div>

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](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](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-

---

<div class="post-metadata">

**Author:** ![Toshko\_Andreev](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/t/3ec8ea/32.png) [@Toshko\_Andreev](https://discourse.orthanc-server.org/u/Toshko_Andreev)\
**Post date:** [February 24, 2016, 9:40am UTC](https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358/3 "2016-02-24T09:40:22Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jodogne](https://discourse.orthanc-server.org/user_avatar/discourse.orthanc-server.org/jodogne/32/1511_2.png) [@jodogne](https://discourse.orthanc-server.org/u/jodogne)\
**Post date:** [February 24, 2016, 9:45am UTC](https://discourse.orthanc-server.org/t/postgresql-exceptions-after-time/358/4 "2016-02-24T09:45:47Z")

</div>

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/](https://bitbucket.org/sjodogne/orthanc/issues/15/)

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