|Pathologically Eclectic Rubbish Lister|
Calls to Apache::Request's param method sometimes end the program and return no databy cfreak (Chaplain)
|on Dec 02, 2004 at 18:08 UTC||Need Help??|
cfreak has asked for the
wisdom of the Perl Monks concerning the following question:
I have a large mod_perl program that uses Apache::Request. My site is getting ready to go live and as more and more people are in it, testing, adding data, etc. I've started seeing instances where something is clicked and nothing happens (Firefox is the browser). Other people are reporting this behavior as well.
After testing for two days I finally discovered that this seems to appear when I make a call to $apr->param('someparam');. Warnings just before the call appear in the log correctly but on some requests it does not continue past this point. Instead of getting an error in the logs or to the browser, its as though nothing happened.
My code is too long to post all of it here but here's the basic setup:
Oh and basically all SWMetal::Init does is, use WSC::Common as its base and define some functions. Common uses several modules as its base and connects to the database. Then it returns a blessed reference that contains the database handle, the conf and the apr passed to it. Calls to SWMetal::Init->new() return $self->SUPER::new().
The problem doesn't happen everytime, if it happens, often clicking the link or button again will get it to go on through. I'm completely stumped.... anyone seen behavior like this before?
UPDATE I found in the main error log that the children of these requests are actually segfaulting :(. I have a backtrace, looks like the segfault occurs in the request table ... not really sure how to fix the problem, hopefully someone on the mod_perl list can help me ...