in reply to Re: debugging mod_perl?
in thread debugging mod_perl?

Those errors were primaraly from threads that somehow froze and were forced to quit during shutdown. Apache::Session tried to save the data from the tied hash and failed because the database had already been shut down... at least that's my interpretation.


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

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

Replies are listed 'Best First'.
Re: Re: Re: debugging mod_perl?
by perrin (Chancellor) on May 19, 2003 at 04:48 UTC
    Hmmm. Why is your server being shut down in the middle of handling requests? Are you sure that you're completely destroying the session object every time? You could have a scoping problem that prevents Apache::Session from saving.
[reply]
      That's the question I'm trying to answer... sometimes I'll request the page and it will just sit there... I'll never get a reply (this from a process that should reply almost instantly.) I can't find any loops it could concievably be getting stuck in.


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

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

[reply]
        That really sounds like a problem with scoping of Apache::Session objects to me. Try removing the session code or explicitly undef'ing your session object at the end of the request. Or put in some warnings in Apache::Session to see if DESTROY is being called.
[reply]

In Section Seekers of Perl Wisdom