# Any reason for a Postgres timeout after 1min?

**URL:** <https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568>\
**Category:** Support\
**Created:** [July 7, 2020, 10:55pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568 "2020-07-07T22:55:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arwesterinen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/arwesterinen/32/40_2.png) [@arwesterinen](https://community.stardog.com/u/arwesterinen)\
**Post date:** [July 7, 2020, 10:55pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/1 "2020-07-07T22:55:25Z")

</div>

When issuing a Virtual Graph query to a Postgres DB, we are getting a "Gateway Time-out" for any queries lasting more than one minute. Our query timeout for Stardog is set to 20 mins.

Is there anything that we can set to address this in the JDBC, to extend/negotiate this?

Andrea

---

<div class="post-metadata">

**Author:** ![zachary.whitley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zachary.whitley/32/94_2.png) [@zachary.whitley](https://community.stardog.com/u/zachary.whitley)\
**Post date:** [July 7, 2020, 11:17pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/2 "2020-07-07T23:17:59Z")

</div>

Is that coming from the Stardog logs or from your flask app?

---

<div class="post-metadata">

**Author:** ![zachary.whitley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zachary.whitley/32/94_2.png) [@zachary.whitley](https://community.stardog.com/u/zachary.whitley)\
**Post date:** [July 7, 2020, 11:27pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/3 "2020-07-07T23:27:12Z")

</div>

It might be open shift. By default it times out http routes after 30sec

> **[Chapter 16. Configuring OpenShift connection timeout Red Hat...](https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.2/html/managing_and_monitoring_process_server/configuring-openshift-connection-timeout-proc)**
>
> Access Red Hat’s knowledge, guidance, and support through your subscription.

---

<div class="post-metadata">

**Author:** ![arwesterinen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/arwesterinen/32/40_2.png) [@arwesterinen](https://community.stardog.com/u/arwesterinen)\
**Post date:** [July 8, 2020, 3:08pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/4 "2020-07-08T15:08:27Z")

</div>

Not in the Stardog logs. And, we are using Django.

Andrea

---

<div class="post-metadata">

**Author:** ![zachary.whitley](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zachary.whitley/32/94_2.png) [@zachary.whitley](https://community.stardog.com/u/zachary.whitley)\
**Post date:** [July 8, 2020, 3:32pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/5 "2020-07-08T15:32:51Z")

</div>

Try the same query through your Django app and then from the Stardog cli running locally on the Stardog server. That should tell you if it's openshift killing the connection or something else.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\
**Post date:** [July 22, 2020, 3:33pm UTC](https://community.stardog.com/t/any-reason-for-a-postgres-timeout-after-1min/2568/6 "2020-07-22T15:33:03Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.