Re: [cgiapp] Re: Apache::DBI and CGI::Application with lots of modules.

[Eric Frazier <ef...@kwinternet.com>]

Hi,

I am learning lots of new things, but still working on the problem itself.
It seems to be the case that even when I am running under ./httpd -X 
I have trouble getting the search  query to get stuck. If I do something
from the mysql monitor like set an order on hold directly with a query, then
the search results won't show the updated status of the order. Yet if from
the web interface, I set the order on hold, then reload, the correct status
is shown. If I restart apache, then the correct status shows. 

Thanks for your advice, I am thinking besides the general advice I have
received, Apache::DB will be my next most helpfull item.

Eric 

At 02:33 PM 10/14/02 -0400, William McKee wrote:
>On 14 Oct 2002 at 9:12, Eric Frazier wrote:
>> That I am not so sure of. I will do some more investigation. It seems like
>> the only variables that could be causing this are the result set from the
>> query and the scalar which holds the html template.  I feel like I know
>> absolutly nothing now :(   I installed Apache::DB but don't yet know what
>> to make of it. 
>
>Hey Eric,
>
>I empathize with you! Getting myself up-to-speed with mod_perl development 
>has been a demanding task. At the moment, my apps have stabilized but I'm 
>sure to hit another hurdle down the road.
>
>As for Apache::DB, read the mod_perl guide at perl.apache.org. The 
>debugger is a pain to learn but has helped me to solve several problems. 
>There is good documentation on using the debugger in the camel book as 
>well. One trick I learned was to let the script run through once using the 
>'c' command. That will load all the scripts and modules into memory which 
>will let you set breaks in your code without having to watch every line go 
>by.
>
>Also, I noticed some folks pointing out some global variables. If you're 
>having troubles tracking these down in your script, you can see all the 
>variables your script has instantiated by using perl-status and looking at 
>the Loaded Modules. Find your CGI::App module in the list and click it to 
>get a detailed list of the arrays, functions, hashes, etc. that it loads.
>
>Good luck,
>William
>
>-- 
> Lead Developer
> Knowmad Services Inc. || Internet Applications & Database Integration
> http://www.knowmad.com
> 
>

(250) 655 - 9513 (PST Time Zone)

"Inquiry is fatal to certainty." -- Will Durant 

Re: [cgiapp] Re: Apache::DBI and CGI::Application with lots of modules.

[William McKee <wi...@knowmad.com>]

On 15 Oct 2002 at 7:12, Eric Frazier wrote:
> I am learning lots of new things, but still working on the problem itself.
> It seems to be the case that even when I am running under ./httpd -X I have
> trouble getting the search  query to get stuck. If I do something from the
> mysql monitor like set an order on hold directly with a query, then the
> search results won't show the updated status of the order. Yet if from the
> web interface, I set the order on hold, then reload, the correct status is
> shown. If I restart apache, then the correct status shows. 

That sounds like trouble. The only problem I've had running httpd -X is 
when I compiled mod_ssl into my server. Apparently, it doesn't like to run 
in single processor mode (although I haven't confirmed this). Otherwise, 
the single processor mode should work just like multi-processor. I'd start 
looking into the code that checks that status.

Good luck,
William

-- 
 Lead Developer
 Knowmad Services Inc. || Internet Applications & Database Integration
 http://www.knowmad.com