# Firewall closes database connections resulting in hung mongrel processes

**URL:** <https://www.ruby-forum.com/t/firewall-closes-database-connections-resulting-in-hung-mongrel-processes/128467>\
**Category:** Rails\
**Created:** [February 7, 2008, 10:57pm UTC](https://www.ruby-forum.com/t/firewall-closes-database-connections-resulting-in-hung-mongrel-processes/128467 "2008-02-07T22:57:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a6a055/32.png) [@matt](https://www.ruby-forum.com/u/matt)\
**Post date:** [February 7, 2008, 10:57pm UTC](https://www.ruby-forum.com/t/firewall-closes-database-connections-resulting-in-hung-mongrel-processes/128467/1 "2008-02-07T22:57:21Z")

</div>

There are actually two separate issues I am experiencing:

- A firewall between our app and database closes the connection behind  
us after 30 mins
- After a period of inactivity oracle closes connections on us

Both of these issues prevent mongrel to respond because rails doesn’t  
realize the connections have been terminated. Anyone experience  
something similar in the past to offer some ideas.

We’ve tried the verification\_timeout setting but it doesn’t apply here  
to Oracle (like MySql). We tried setting the auto\_retry property on  
the OCI8AutoRecover Class with no results. We have even attempted to  
override some default behaviour of AR so that we verify, timeout or  
disconnect connections before executing a query but still have not had  
successful results.
