> If I want to run mp1 and mp2 on the same web server, I'm guessing I'll
> need different perl trees. Is there anything I should be concerned with in
> a setup like this? Memory issues or anything of the sort?
I'm running both apache1.3/mp1 and apache2/mp2 on my development
sandbox. I use the same
Quick question. I hope this hasn't been asked a million times already.
If I want to run mp1 and mp2 on the same web server, I'm guessing I'll
need different perl trees. Is there anything I should be concerned with in
a setup like this? Memory issues or anything of the sort?
For instance,
apache
"Jonathan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> how many connections do you get from a show processlist in mysql?
It looks right, show processlist counts connections * processes, even during
a stress test.
> is it possible that some scoping issue had the connect occuri
how many connections do you get from a show processlist in mysql?
is it possible that some scoping issue had the connect occuring
during prefork, instead of postfork, and mysql is dying from apache
trying to do everything via 1 persistent connection?
From: "Jonathan" <[EMAIL PROTECTED]>
Subject: Re: Apache::Session::MySQL lock troubles
> looks like DBI stops talking to mysql
>
> when this happens, is apache hanging?
>
> or does it just crash on one page, and then continually crash on
> subsequent pages?
Yeah, apache freezes ( was freezing )
On Sun, 26 Feb 2006 22:08:56 +
Leo Lapworth <[EMAIL PROTECTED]> wrote:
> On 26 Feb 2006, at 20:42, [EMAIL PROTECTED] wrote:
>
> > Good conversations...
> >
> > One question that I keep asking myself about RAD frameworks like
> > Catalyst is yeah, they're nice to develop a quick solution but
fyi , you can also see that in a regular mysql client
show processlist
this could also be a pure mysql problem. mysql is a fast db, but its
got some weird bugs.
i kept having issues with a collation matching problem on a table,
because I needed to change the column defaults from
looks like DBI stops talking to mysql
when this happens, is apache hanging?
or does it just crash on one page, and then continually crash on
subsequent pages?
a few ideas:
a
are you using the same dh / $dbh for session as the rest of
your site?
if so,
On 26 Feb 2006, at 20:42, [EMAIL PROTECTED] wrote:
Good conversations...
One question that I keep asking myself about RAD frameworks like
Catalyst is yeah, they're nice to develop a quick solution but how
well do they scale?
In particular, I'd like to use Catalyst but I haven't seen much
Apache::Session is occasionally hanging pages. If I stop the server, I find
the following in the error log:
http://waveright.homeip.net/~trwww/code/pmsi/4tp-bug.txt
using pre and post statment warn()s, I found that the line that causes the
hang is:
eval {
tie %{$session}, 'Apache::Se
Good conversations...
One question that I keep asking myself about RAD frameworks like Catalyst is
yeah, they're nice to develop a quick solution but how well do they scale?
In particular, I'd like to use Catalyst but I haven't seen much traffic about
large application success stories...
_
11 matches
Mail list logo