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:[email protected]] 
Sent: Tuesday, February 21, 2006 6:39 PM
To: MySQL Win32 List
Subject: Re: Maximum Time Reached

On 2/21/06, Vic Spainhower <[email protected]> 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/[email protected]


-- 
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:    http://lists.mysql.com/[email protected]