Background: I have a fairly complex distributed Django application that, for excellent reasons that I can not go into, requires that it have as low an attack surface as possible AND that it run on both Windows and Linux. One consequence of this is that instead of using any of the normal tools for building and managing distributed applications (ie: RabbitMQ + Celery + django-celery) I've chosen to roll my own infrastructure. It all works remarkably well, except for one part, and I'm looking for some advice in that area.
Much of the application is using SQLite for persistance, but the correlation aspects of the application use Oracle. Each piece of the application has a web server (either Apache/mod-python or CherryPy) and a background job processor. The job processor pulls tasks off a queue, runs them, then reschedules them as necessary. Most of these tasks interact with the database through Django. Each individual task is effectively sharing a single Problem: The problem that I'm currently facing is that occasionally an Oracle instance will get reset (for any number of good reasons), but the background process continues to attempt to use it's connection Object, resulting in errors until I detect the problem and restart the background process. What I would like to be able to do is to have my background process close and/or reset its database connection, as often as necessary. Thank you in advance for any assistance you can render. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
