xinhuan
>
> From: Perrin Harkins
> Date: Thursday, June 27, 2013 3:05 PM
> To: xiaolan
> Cc: "modperl@perl.apache.org"
> Subject: Re: mysql connection pooling
>
> Hi,
>
> There is nothing exactly like the database pool in JDBC. However, there
> are so
;
mailto:modperl@perl.apache.org>>
Subject: Re: mysql connection pooling
Hi,
There is nothing exactly like the database pool in JDBC. However, there are
solutions for this problem.
The first thing you should do is run a reverse proxy in front of your mod_perl
server. That typically reduce
Thank you Perrin.
Yes I should use Nginx as a reverse-proxy for modperl appservers, but I
don't yet. I will check it.
Thanks.
On Fri, Jun 28, 2013 at 3:05 AM, Perrin Harkins wrote:
> Hi,
>
> There is nothing exactly like the database pool in JDBC. However, there
> are solutions for this proble
Hi,
There is nothing exactly like the database pool in JDBC. However, there
are solutions for this problem.
The first thing you should do is run a reverse proxy in front of your
mod_perl server. That typically reduces the number of mod_perl processes
by a factor of 10, i.e. 1000 mod_perl proces
Hi Philip,
On zondag, apr 10, 2005, at 22:42 Europe/Amsterdam, Philip M. Gollucci
wrote:
The auto_reconnect behavior was changed in DBD::mysql or DBI recently
(< 6 months ago)... I forget from/to.. Read the Changes of each.
There's some info in DBD::mysql. Further investigation tells me this
m
Hi Harm,
On zondag, apr 10, 2005, at 10:53 Europe/Amsterdam, harm wrote:
DBD::mysql::st execute failed: MySQL server has gone away at
/opt/ttgp/dev/webapp/ttgp/smsclient/perl/sms line 111.
This happens after several hours of idle time in the webserver.
looks like a connection timeout. Try:
$dbh->{'
On Sun, Apr 10, 2005 at 10:25:58AM +0200, Bas Schulte wrote:
> Hi all,
>
> I've been using Apache/mod_perl/MySQL combined with Apache::DBI for
> years, and it has been working like a charm. However, while preparing
> for a new release of the system I built, I'm getting this:
>
> DBD::mysql::st
David Arnold wrote:
All,
What should I be reading if I want to learn how to use modperl 2.0 with
mysql?
You just use it as with any other perl program. The only thing you want to use
is Apache::DBI and a few other nuances explained here
http://perl.apache.org/docs/1.0/guide/databases.html
--
On Tue, 23 Mar 2004 11:47:01 -0500, Jamie LeTual wrote:
> This won't help if the database is running on a different machine. If
> the apache and mysql are on the same machine, this will work although
> there are security concerns regarding this.
Good points. I can live with the limitations for
Hi,
> Well, I tried increasing the max packet size, but all that did was decrease
> the frequency of the problem appearing. I increased it from 1MB to 8MB.
> Think that was enough?
You never send us a code fragment did you? The thing puzzling me is
"decrease the frequency"... I agree with Andrew
Andrew Green wrote:
Frankly, if you're not sure of an upper limit to the size of data you
might need to try to write to the database, sooner or later you're bound
to have to try to send something too big. I'd really suggest looking
into the Storable or FreezeThaw CPAN modules as a way of just dum
On Tue, 23 Mar 2004 10:25:12 -0500, Chris Miller wrote:
> Well, I tried increasing the max packet size, but all that did was
> decrease the frequency of the problem appearing.
I guess that's a pretty good indication that it was the packet size
problem biting you!
Frankly, if you're not sure of a
start apache and it fixes the problem.
Thanks,
Chris Miller
Compuville
www.compuville.net
-Original Message-
From: Chris Miller [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 10:55 AM
To: 'Andrew Green'
Cc: [EMAIL PROTECTED]
Subject: RE: "MySQL server has
On Thu, 18 Mar 2004 10:55:29 -0500, Chris Miller wrote:
> Think I should up the max packet size??
I think by default it's 1MB, so maybe. I'm not sure of why the default
is what it is, and what might break through changing it.
In the system I was developing, I was trying to store a serialised P
On Thu, 18 Mar 2004 11:03:42 -0500, Perrin Harkins wrote:
> Are you using Apache::DBI? It should just reconnect automatically when
> this happens.
I didn't know that. Mind you, I shouldn't think the too-big record
would have been written to the database, which could be a problem.
Cheers,
Andre
2004 10:55 AM
> To: Chris Miller
> Cc: [EMAIL PROTECTED]
> Subject: Re: "MySQL server has gone away"
>
> On Thu, 18 Mar 2004 10:23:42 -0500, Chris Miller wrote:
>
> > DBD::mysql::st execute failed: MySQL server has gone away at
> > /usr/local/lib/perl/5.6.1/Mysql
On Thu, 2004-03-18 at 10:23, Chris Miller wrote:
> DBD::mysql::st execute failed: MySQL server has gone away at
> /usr/local/lib/perl/5.6.1/Mysql.pm line 175.
Are you using Apache::DBI? It should just reconnect automatically when
this happens.
- Perrin
--
Report problems: http://perl.apache.o
Think I should up the max packet size??
Thanks,
Chris Miller
Compuville
www.compuville.net
-Original Message-
From: Andrew Green [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 10:55 AM
To: Chris Miller
Cc: [EMAIL PROTECTED]
Subject: Re: "MySQL server has gone away&quo
On Thu, 18 Mar 2004 10:23:42 -0500, Chris Miller wrote:
> DBD::mysql::st execute failed: MySQL server has gone away at
> /usr/local/lib/perl/5.6.1/Mysql.pm line 175.
I was bitten by this once when trying to write records to the MySQL
server that were bigger than the server's configured maximum p
19 matches
Mail list logo
