No, this a hand-rolled server. I found a solution that seems to work.
Rather than "use"ing DBI at the top level of the script, I "require" it in the child process, after forking. With limited testing, this appears to allow multiple threads to independently access the database. Unfortunately, the CHLD signal handling that so nicely lets me keep track of the child processas as the come and go, does not appear to be working under Win2K, but that is not fatal. Bob --- Simon Oliver <[EMAIL PROTECTED]> wrote: > Is your server Net::Daemon or PlRPC based? If so > then it is that that is > causing the problem, not DBI or the DBD. There are > reports that this may be > fixed in the latest ActiveState Perl. I have not > had chance to check this > yet. > > Not Specified wrote: > > > > I have written a Perl server that acts as a > gateway > > to a MySQL database. When clients connect, the > > server forks a child (which connects to the db, > > processes the client's request, disconnects from > > the db and exits). This works great under LINUX > > with real processes. > > > > Moving to Windows (2000), I have found that the > > ActiveState fork emulation (i.e. threads) does > > not work so well. Once the first client has > > exited, no other clients can connect. Also, while > > the first client is connected, no other clients > > can connect. So, it seems that there is an issue > > with threads and DBI or DBD-Mysql. > > > > I have seen this issues raised on many mailing > lists > > but with no authoritative resolution. > > > > Can anyone shed some light on this? > > > > Is is DBI or DBD-Mysql? Is it ActiveState Perl? > > > > Thanks, > > > > Bob > > > > __________________________________________________ > > Do You Yahoo!? > > Great stuff seeking new owners in Yahoo! Auctions! > > http://auctions.yahoo.com __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
