Maximum Time Reached

Maximum Time Reached

am 22.02.2006 01:45:51 von Vic Spainhower

------=_NextPart_000_01EA_01C63706.46C00A80
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_01EB_01C63706.46C27B80"


------=_NextPart_001_01EB_01C63706.46C27B80
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello,

I am using a MySQL database on my web site which for the most part is
working quite well. However, every so often (but way to often) when starting
a new form it will just stop until the 30 second maximum time is reached.
When I Press the refresh key the form is immediately displayed. It is as if
some sort of lock was set and when max time is reached it gets unlocked and
continues. This doesn't happen on any particular form as it can happen
anywhere in the application.

I'm going to throw this in just in case it may be related. I use SQLyog and
it will also experience these 30 second delays (i don't get the max time
message) when I'm just trying to view a table. It seems to happen when I
don't use it for a while and the first table that I view will take 30
seconds to view after which it will perform OK as long as I don't pause for
a while. When using MySQL Administrator I don't see any of these problems
and the support at SQLyog are baffled because the SQLyog engine is the same
as MySQL Administrator.

Any ideas as to how I can resolve this???

The provider is running MySQL version 4.1.10

Thanks,



Vic






------=_NextPart_001_01EB_01C63706.46C27B80
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Clear Day
charset=3Dus-ascii">




Hello,


I am using a MySQL database on my =
web site=20
which for the most part is working quite well. However, every so often =
(but way=20
to often) when starting a new form it will just stop until the 30 =
second=20
maximum time is reached. When I Press the refresh key the form is =
immediately=20
displayed. It is as if some sort of lock was set and when max time is =
reached it=20
gets unlocked and continues. This doesn't happen on any particular form =
as it=20
can happen anywhere in the application.


I'm going to throw this in just in =
case it may=20
be related. I use SQLyog and it will also experience these 30 second =
delays (i=20
don't get the max time message) when I'm just trying to view a =
table. It=20
seems to happen when I don't use it for a while and the first table that =
I view=20
will take 30 seconds to view after which it will perform OK as long as I =
don't=20
pause for a while. When using MySQL Administrator I don't see any of =
these=20
problems and the support at SQLyog are baffled because the SQLyog engine =
is the=20
same as MySQL Administrator.


Any ideas as to how I can resolve=20
this???


The provider is running MySQL=20
version 4.1.10


class=3D015062000-22022006>Thanks,


 


Vic


 


 



------=_NextPart_001_01EB_01C63706.46C27B80--

------=_NextPart_000_01EA_01C63706.46C00A80--

Re: Maximum Time Reached

am 22.02.2006 03:38:47 von Daniel da Veiga

On 2/21/06, Vic Spainhower wrote:
>
>
> Hello,
>
> I am using a MySQL database on my web site which for the most part is
> working quite well. However, every so often (but way to often) when start=
ing
> a new form it will just stop until the 30 second maximum time is reached.
> When I Press the refresh key the form is immediately displayed. It is as =
if
> some sort of lock was set and when max time is reached it gets unlocked a=
nd
> continues. This doesn't happen on any particular form as it can happen
> anywhere in the application.
>
> I'm going to throw this in just in case it may be related. I use SQLyog a=
nd
> it will also experience these 30 second delays (i don't get the max time
> message) when I'm just trying to view a table. It seems to happen when I
> don't use it for a while and the first table that I view will take 30
> seconds to view after which it will perform OK as long as I don't pause f=
or
> a while. When using MySQL Administrator I don't see any of these problems
> and the support at SQLyog are baffled because the SQLyog engine is the sa=
me
> as MySQL Administrator.
>
> Any ideas as to how I can resolve this???

You seem to be reaching the timeouts, not only of your web server, but
with MySQL too, try setting the interactive and wait timeout (check
for these variables at the config file) to a higher value, MySQL
administrator and query browser set it to a high value upon connect,
wich might explain why your other apps get it and the MySQL ones
don't.

Its the only reason I can think of (besides DNS resolution, but that
would be a blind shot).

Try it and let us know...

>
> The provider is running MySQL version 4.1.10

Oh gosh, UPGRADE it!!! There is a bug with MySQL 4.1.x (where X is <=3D
11) and specific queries that would crash the connection, damn, I
suffered for a whole month before they released 4.1.11 and it solved
my problems. If you hasn't mentioned it, I would not remember...

>
> Thanks,
>
>
>
> Vic
>
>
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Maximum Time Reached

am 22.02.2006 04:00:52 von Vic Spainhower

>> try setting the interactive and wait timeout (check for these variables
at the config file) to a higher value

Thanks Daniel,

Wouldn't that just cause it to wait longer but still not resolve the
problem?? Seems I need to resolve why the long wait is occuring because as
soon as it maxes out the screen will refresh when I hit refresh. Maybe it's
MySQL 4.1.10 that's causing the problem but somehow I've got to convince my
provider to put up a later version of MySQL.

Thanks,

Vic

-----Original Message-----
From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]
Sent: Tuesday, February 21, 2006 6:39 PM
To: MySQL Win32 List
Subject: Re: Maximum Time Reached

On 2/21/06, Vic Spainhower wrote:
>
>
> Hello,
>
> I am using a MySQL database on my web site which for the most part is
> working quite well. However, every so often (but way to often) when
> starting a new form it will just stop until the 30 second maximum time is
reached.
> When I Press the refresh key the form is immediately displayed. It is
> as if some sort of lock was set and when max time is reached it gets
> unlocked and continues. This doesn't happen on any particular form as
> it can happen anywhere in the application.
>
> I'm going to throw this in just in case it may be related. I use
> SQLyog and it will also experience these 30 second delays (i don't get
> the max time
> message) when I'm just trying to view a table. It seems to happen when
> I don't use it for a while and the first table that I view will take
> 30 seconds to view after which it will perform OK as long as I don't
> pause for a while. When using MySQL Administrator I don't see any of
> these problems and the support at SQLyog are baffled because the
> SQLyog engine is the same as MySQL Administrator.
>
> Any ideas as to how I can resolve this???

You seem to be reaching the timeouts, not only of your web server, but with
MySQL too, try setting the interactive and wait timeout (check for these
variables at the config file) to a higher value, MySQL administrator and
query browser set it to a high value upon connect, wich might explain why
your other apps get it and the MySQL ones don't.

Its the only reason I can think of (besides DNS resolution, but that would
be a blind shot).

Try it and let us know...

>
> The provider is running MySQL version 4.1.10

Oh gosh, UPGRADE it!!! There is a bug with MySQL 4.1.x (where X is <=
11) and specific queries that would crash the connection, damn, I suffered
for a whole month before they released 4.1.11 and it solved my problems. If
you hasn't mentioned it, I would not remember...

>
> Thanks,
>
>
>
> Vic
>
>
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE
Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE
BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=vic@perfected.com


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: Maximum Time Reached

am 22.02.2006 14:58:23 von Daniel da Veiga

On 2/22/06, Vic Spainhower wrote:
> >> try setting the interactive and wait timeout (check for these variab=
les
> at the config file) to a higher value
>
> Thanks Daniel,
>
> Wouldn't that just cause it to wait longer but still not resolve the
> problem?? Seems I need to resolve why the long wait is occuring because =
as
> soon as it maxes out the screen will refresh when I hit refresh. Maybe i=
t's
> MySQL 4.1.10 that's causing the problem but somehow I've got to convince =
my
> provider to put up a later version of MySQL.

That would be in fact pretty simple *grin*...
Find a faulty SQL and issue it a couple hundred times from console
*grin a little more*, then ask for the admin to take a look at the
error log for warnings on closed faulty connections. I say that
because my app would fail, so I got the SQL and entered it at console,
the good thing about the console is that once it failts, it retries
the query (retrying the connection), and it works (because for some
reason the second time works, exactly as you described.

I'm not quite sure, but the SQL that would fail a lot was a SELECT,
with WHERE, ORDER BY and LIMIT clauses. Try it from console and see
how it will behave. If it fails, you know its the version, else, well,
back to debug times.

>
> Thanks,
>
> Vic
>
> -----Original Message-----
> From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]
> Sent: Tuesday, February 21, 2006 6:39 PM
> To: MySQL Win32 List
> Subject: Re: Maximum Time Reached
>
> On 2/21/06, Vic Spainhower wrote:
> >
> >
> > Hello,
> >
> > I am using a MySQL database on my web site which for the most part is
> > working quite well. However, every so often (but way to often) when
> > starting a new form it will just stop until the 30 second maximum time =
is
> reached.
> > When I Press the refresh key the form is immediately displayed. It is
> > as if some sort of lock was set and when max time is reached it gets
> > unlocked and continues. This doesn't happen on any particular form as
> > it can happen anywhere in the application.
> >
> > I'm going to throw this in just in case it may be related. I use
> > SQLyog and it will also experience these 30 second delays (i don't get
> > the max time
> > message) when I'm just trying to view a table. It seems to happen when
> > I don't use it for a while and the first table that I view will take
> > 30 seconds to view after which it will perform OK as long as I don't
> > pause for a while. When using MySQL Administrator I don't see any of
> > these problems and the support at SQLyog are baffled because the
> > SQLyog engine is the same as MySQL Administrator.
> >
> > Any ideas as to how I can resolve this???
>
> You seem to be reaching the timeouts, not only of your web server, but wi=
th
> MySQL too, try setting the interactive and wait timeout (check for these
> variables at the config file) to a higher value, MySQL administrator and
> query browser set it to a high value upon connect, wich might explain why
> your other apps get it and the MySQL ones don't.
>
> Its the only reason I can think of (besides DNS resolution, but that woul=
d
> be a blind shot).
>
> Try it and let us know...
>
> >
> > The provider is running MySQL version 4.1.10
>
> Oh gosh, UPGRADE it!!! There is a bug with MySQL 4.1.x (where X is <=3D
> 11) and specific queries that would crash the connection, damn, I suffere=
d
> for a whole month before they released 4.1.11 and it solved my problems. =
If
> you hasn't mentioned it, I would not remember...
>
> >
> > Thanks,
> >
> >
> >
> > Vic
> >
> >
> >
> >
>
>
> --
> Daniel da Veiga
> Computer Operator - RS - Brazil
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS =
PE
> Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE
> BLOCK------
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=3Dvic@perfected.com
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=3Ddanieldaveiga@gma=
il.com
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Maximum Time Reached

am 25.02.2006 19:52:17 von Vic Spainhower

Daniel,

OK you're the man - you nailed it!

My provider (HalfPriceHosting.com) refused to update the version 4.1.10 to
anything later so I'm moving my site to a different hosting company
(bluehost.com). I installed MySQL 4.1.18 on my local machine and the
timeouts in the app and extended delays using SQLyog did not occur. I've now
got the site setup on the new host and the problems that I was plagued with
are gone! Performance is great - no more timeouts.

The folks at SQLyog would like to write a FAQ on this problem but we're not
able to locate what was changed in 4.1.11 to correct this issue
http://dev.mysql.com/doc/refman/4.1/en/news-4-1-11.html. Can you identify
the change in 4.1.11 that corrected this issue?

Thanks Daniel, your assistance and expertise is greatly appreciated!

Vic


-----Original Message-----
From: Vic Spainhower [mailto:vic@perfected.com]
Sent: Tuesday, February 21, 2006 7:01 PM
To: 'Daniel da Veiga'; 'MySQL Win32 List'
Subject: RE: Maximum Time Reached

>> try setting the interactive and wait timeout (check for these variables
at the config file) to a higher value

Thanks Daniel,

Wouldn't that just cause it to wait longer but still not resolve the
problem?? Seems I need to resolve why the long wait is occuring because as
soon as it maxes out the screen will refresh when I hit refresh. Maybe it's
MySQL 4.1.10 that's causing the problem but somehow I've got to convince my
provider to put up a later version of MySQL.

Thanks,

Vic

-----Original Message-----
From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]
Sent: Tuesday, February 21, 2006 6:39 PM
To: MySQL Win32 List
Subject: Re: Maximum Time Reached

On 2/21/06, Vic Spainhower wrote:
>
>
> Hello,
>
> I am using a MySQL database on my web site which for the most part is
> working quite well. However, every so often (but way to often) when
> starting a new form it will just stop until the 30 second maximum time
> is
reached.
> When I Press the refresh key the form is immediately displayed. It is
> as if some sort of lock was set and when max time is reached it gets
> unlocked and continues. This doesn't happen on any particular form as
> it can happen anywhere in the application.
>
> I'm going to throw this in just in case it may be related. I use
> SQLyog and it will also experience these 30 second delays (i don't get
> the max time
> message) when I'm just trying to view a table. It seems to happen when
> I don't use it for a while and the first table that I view will take
> 30 seconds to view after which it will perform OK as long as I don't
> pause for a while. When using MySQL Administrator I don't see any of
> these problems and the support at SQLyog are baffled because the
> SQLyog engine is the same as MySQL Administrator.
>
> Any ideas as to how I can resolve this???

You seem to be reaching the timeouts, not only of your web server, but with
MySQL too, try setting the interactive and wait timeout (check for these
variables at the config file) to a higher value, MySQL administrator and
query browser set it to a high value upon connect, wich might explain why
your other apps get it and the MySQL ones don't.

Its the only reason I can think of (besides DNS resolution, but that would
be a blind shot).

Try it and let us know...

>
> The provider is running MySQL version 4.1.10

Oh gosh, UPGRADE it!!! There is a bug with MySQL 4.1.x (where X is <=
11) and specific queries that would crash the connection, damn, I suffered
for a whole month before they released 4.1.11 and it solved my problems. If
you hasn't mentioned it, I would not remember...

>
> Thanks,
>
>
>
> Vic
>
>
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE
Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE
BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=vic@perfected.com


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=vic@perfected.com


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org