Perrin Harkins wrote:
> You could still be foiling it
> by stashing database handles in globals or closures though.
Thanks a lot, Perrin, in fact this helped a lot. You convinced me that
it's my error :)
The idea that one db handle is being inherited by the forked childs
helped. I finally found
On Thu, 2004-05-27 at 21:34, Mike Blazer wrote:
> It's hard to extract the part of the code because my configs look wild
> :)
Holy cow, this is a lot of code. The simplest thing I can think of to
see what's going on is to turn on Apache::DBI debugging and then watch
your error_log. If you see a
Thanks, Perrin, I'm sure you're right just don't see where this happens.
It's hard to extract the part of the code because my configs look wild
:)
One sh script starts/stops/restarts 3 servers with 1 config for proxy
and 1 config full of sections - for two back-end servers.
Yes, I do call mysql f
On Thu, 2004-05-27 at 15:20, Mike Blazer wrote:
> See, in the very beginning - 3 child processes started and connected to
> the same mysql thread_id
>
> None of my processes ever disconnects, they all use Apache:DBI and
> everything is checked to be correct.
> Seems like it's mysql error in dispat
Hello, guys!
I use this configuration for quite a while and under a hard traffic:
Apache 1.3.29
mod_perl 1.29
mysql 4.0.3 (a rather old one)
for sometime I have this minor problem - each time I restart servers
there are few failures right after the restart. It's always "Lost
connection" error. As
