I've been running with the kill-safe-connection's for a few weeks now.<div><br></div><div>This seems to have fixed the problem, or at least hidden it to a point that I no longer am affected by it.</div><div><br></div> <div>Thanks for your help.<br><br><div class="gmail_quote">On Thu, Feb 2, 2012 at 2:53 AM, Ryan Culpepper <span dir="ltr"><<a href="mailto:ryan@cs.utah.edu">ryan@cs.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="HOEnZb"><div class="h5">On 02/01/2012 10:09 PM, Curtis Dutton wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm receiving this error after my webserver is running for a few days.<br> <br> Hosting a plt webserver on Ubuntu server, I'm using the racket/db<br> library to access a local postgres database. After a few hundred<br> requests, over a period of days, I eventually get this error message.<br> "query-rows: connection is permanently locked due to a terminated thread"<br> <br> Once this error is generated all calls made to the database then fail,<br> and continue to fail until I restart the webserver process.<br> <br> I am using the virtual connection pooling interface as well.<br> <br> Has anyone seen this yet?<br> <br> I submitted bug #12530.<br> <br> I have not been able to reproduce this manually. It happens after a few<br> days. I'm willing to instrument or hack at it to help determine the<br> issue but a little guidance would be very welcome.<br> </blockquote> <br></div></div> I'll look into it. If the error has a stack trace, that would be very helpful.<br> <br> You could also try wrapping the postgresql connection in a kill-safe-connection proxy. That is, change<br> <br> (postgresql-connect ....)<br> <br> to<br> <br> (kill-safe-connection (postgresql-connect ....))<br> <br> and see if that makes a difference.<span class="HOEnZb"><font color="#888888"><br> <br> Ryan<br> </font></span></blockquote></div><br></div>