This is a know bug with Apache, at least for MySQL and I would
suspect any DB, because the code is on the apache side.
It has to the do with the fact the algorithm that decides whether or
not a given process connection is reusable in a new context (which it
decides that it can't reuse) so it opens a new connection without
closing the old connection(s) in case the MIGHT be reusable in future
attempts, but they never are :(, because the algorithm is broken!
Anyway, the work around is to change the phplib code to use NON-
persistant connections. Just make the change and your problems should
just go away. I think you can just grep ora_plogon * and change the
"ora_plogon" to "ora_logon"
-Steve
On 12 Aug 2002 at 14:11, Arnar Gestsson wrote:
> Hi there,
>
> I have been using db_oracle.inc from phplib which uses persistent
> connection to the DB. Occationally I have got errors stating that no
> more connections to the db are available. From the documentation I
> gather that
>
> "there will be at most "number of web server processes" times "number of
> Host/Username/Password-combinations" many simultaneous connections to
> your database server"
>
> which means that for an apache server you can end up with tenths or
> hundreds of connections, don't you? Is there a solution that keeps this
> below certain numbers. My system consists of
>
> OS: Linux RH 7.x
> Webserver: apache 1.3.2x
> php: 4.x as mod_php
>
> BR Arnar
>
> ----------------------------------------------------------------
> Arnar Gestsson MSEE
> Project Manager - TrackWell Software/Stefja
> e: ar...@tr...
> s: 5100605
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phplib-users
>
|
