in reply to Re: Re: mysql, locked databases, Apache::DBI and mod_perl
in thread mysql, locked databases, Apache::DBI and mod_perl

Can you give more explanation of "things go wrong"? What happens, exactly? Does it hang? Do you get error messages?
  • Comment on Re: Re: Re: mysql, locked databases, Apache::DBI and mod_perl

Replies are listed 'Best First'.
Re: Re: Re: Re: mysql, locked databases, Apache::DBI and mod_perl
by Flame (Deacon) on May 20, 2003 at 21:11 UTC
    As I said before, it just stops, like it got itself stuck in a loop.



    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

      Sounds like you are having problems with Apache::Session's locking system because the session object isn't being destroyed at the end of a request in some situation. It could be that you accidentally made a closure somewhere that holds the %state hash.

      The shotgun solution is to simply stop using Apache::Session's locking. Change from Apache::Session::MySQL to Apache::Session::Flex or just change Apache::Session::MySQL itself and use the NullLocker instead of the MySQL locker. However, that might mask the larger problem which is that your session data doesn't get saved when the object doesn't get destroyed.