Re: Re: debugging mod_perl?

[Flame]

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)

[perrin]

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.

[Flame]

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)

[perrin]

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.