Re: Re: timeout from UserAgent from mod

OK, I will look at FastCGI, but in particuliar, I wanted
the DBI connection pooling mod_perl offers.

However, just to be clear on this, only the first page
was a .plx (mod_perl) script. No matter if the second page
the GET is done to is a .html (static page) or
another .plx, the result is the same. And if the second
page *IS* a .plx, it *does* execute (I generate some
logging) normally - only its response seems to be lost.

I was thinking the multi-threading was working, except for
the socket stuff, which (as I mentioned) might be suspect.

Geoff

Comment on Re: Re: timeout from UserAgent from mod_perl

Replies are listed 'Best First'.
Re: Re: Re: timeout from UserAgent from mod_perl by perrin (Chancellor) on Nov 20, 2001 at 09:10 UTC
mod_perl does not offer connection "pooling" exactly. It simply keeps connections persistent. You can do something similar in FastCGI by putting your database connections into a global and leaving them open, or using the connect_cached method of DBI. If you've set the threads to 1, you'll have problems no matter what kind of page you're fetching. If you haven't, the socket stuff will give you trouble. If you really want to use mod_perl, I strongly suggest you look at how to get rid of this need for LWP requests. It's going to be a performance killer, and you can probably do it with a subrequest or something.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: timeout from UserAgent from mod_perl
by perrin (Chancellor) on Nov 20, 2001 at 09:10 UTC

If you've set the threads to 1, you'll have problems no matter what kind of page you're fetching. If you haven't, the socket stuff will give you trouble.

If you really want to use mod_perl, I strongly suggest you look at how to get rid of this need for LWP requests. It's going to be a performance killer, and you can probably do it with a subrequest or something.

[reply]