Germer, Carsten wrote at 2005-10-24 13:32 +0200:
>Ok, that's a bit much for my question I guess...
>I gather from all your mails that I can not "close" a database
>connection periodically or on event from Zope (Script or whatever)?
Modulo bugs, this happens automatically (when the DA object is flu
Germer, Carsten wrote:
Ok, that's a bit much for my question I guess...
I gather from all your mails that I can not "close" a database
connection periodically or on event from Zope (Script or whatever)?
Any hands-down clues what I can do to prevent db-conns from ideling
around?
Fewer database i
--Original Message-
>From: Dieter Maurer [mailto:[EMAIL PROTECTED]
>Sent: Saturday, October 22, 2005 8:07 PM
>To: Matthew T. Kromer
>Cc: Chris Withers; Germer, Carsten; zope-db@zope.org
>Subject: Re: [Zope-DB] Closing idle DCoracle2 Connections?
>
>
>Matthew T. Kromer wrote at 200
Matthew T. Kromer wrote at 2005-10-21 20:39 -0400:
> ...
>What happens with Zope and DCOracle2 I think is when the DA
>connection object is ghosted, it doesn't know about it, and thus
>doesn't close its connection.
Why not?
When the DA instance is ghosted, the "db" object is deleted
(last
However, a colleague found out that for his (probably special kind
of) setup, "cxOracle" was much slower than DCOracle2 (by about
a factor of 4).
heh, well I like to write FAST code when I can ;) However, the Zope
DA/RDBMS machinery slows the db conection down enormously -- like 9x
if
Chris Withers wrote at 2005-10-21 16:27 +0100:
> ...
>Well, it depends, there can be a need for lots of infrequently used DA's
>connecting to the same database.
What prevents to replace these DA's by a single instance?
Looks much easier than a sophisticated connection pool management...
>Having
Cynthia Kiser wrote at 2005-10-20 19:09 -0700:
> ...
>I am pretty sure there is a bug in DCOracle2. If you can, try using
>DCOracle2 from the python prompt and close the connection. Now, can
>you still talk to the database? It seemed to me that I could when I
>tried that.
>
>For my particular circ
Dieter Maurer wrote:
Usually, there is not need for a sophisticated connection
management. Just do not create unnecessary DA instances.
Yes, this is the most common mistake...
Bugs should be fixed and not worked around with more complex
software (complex connection management).
Well, it dep
Cynthia Kiser wrote:
open. FYI just closing the database connection via the ZMI does not
release the idle connections Oracle still sees.
Yes, that button actually does nothing ;-)
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Quoting Germer, Carsten <[EMAIL PROTECTED]>:
> Hello everyone,
>
> As we start to use our zope-Ora connection more frequently our database
> administrator complains that he sees a lot of idle conections.
I am pretty sure there is a bug in DCOracle2. If you can, try using
DCOracle2 from the python
Germer, Carsten wrote at 2005-10-20 11:16 +0200:
> ...
>As we start to use our zope-Ora connection more frequently our database
>administrator complains that he sees a lot of idle conections.
>
>I know theres "connection.close()" in DCOra2 but does anyone know of a
>way to autmatically close a DCOr
11 matches
Mail list logo
