#14298: maximum open cursors exceeded on Jython and Oracle
--------------------------------------------------------+-------------------
Reporter: stephanekonstantaropoulos | Owner: xoror
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Oracle Jython
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 1 |
--------------------------------------------------------+-------------------
Comment (by josh.smeaton@…):
I think I found the ultimate cause of this issue. Well, I didn't find it,
but I found a reference to it elsewhere.
http://bugs.jython.org/issue1582
That describes a memory leak where cursors aren't able to be finalised if
not explicitly closed. It has to do with the zx DB drivers. My assumption
is that since the cursors aren't being finalised, the finaliser is not
calling close. And since django doesn't explicitly call close in all
cases, they aren't able to be finalized. The bug above has a patch
associated with it. I'll research this more and see if it has already been
fixed properly in the zxjdbc drivers, and if so, try to migrate that into
the django-on-java project.
--
Ticket URL: <http://code.djangoproject.com/ticket/14298#comment:13>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
