Re: trying to change wait_timeout
That's the ticket! Thanks On 09/08/2011 06:55 AM, Andrew Moore wrote: Check that you're looking at the variable in the GLOBAL scope not the SESSION scope. SHOW GLOBAL VARIABLE ... Andy On Thu, Sep 8, 2011 at 11:34 AM, Bruce Ferrellbferr...@baywinds.orgwrote: On 09/08/2011 02:56 AM, Johan De Meersman wrote: - Original Message - From: Bruce Ferrellbferr...@baywinds.org** To: mysql@lists.mysql.com Sent: Thursday, 8 September, 2011 3:10:16 AM Subject: trying to change wait_timeout I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] That, and restart the service, of course. You *did* think of restarting the service, I trust? :-p That being said, it is also a dynamic variable, so if you didn't restart, prefer not to restart *and* are certain your config file is correct; you can also do set global wait_timeout=xxx to have it take effect immediately for all new sessions. Yes, that means you'll have to disconnect/reconnect to see the change in your own session. Good question to ask. Yes, I did restart mysql. Both before and after show variables like 'wait_time%' returns 28800. Most confusing. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?** unsub=eroomy...@gmail.comhttp://lists.mysql.com/mysql?unsub=eroomy...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: trying to change wait_timeout
- Original Message - From: Bruce Ferrell bferr...@baywinds.org To: mysql@lists.mysql.com Sent: Thursday, 8 September, 2011 3:10:16 AM Subject: trying to change wait_timeout I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] That, and restart the service, of course. You *did* think of restarting the service, I trust? :-p That being said, it is also a dynamic variable, so if you didn't restart, prefer not to restart *and* are certain your config file is correct; you can also do set global wait_timeout=xxx to have it take effect immediately for all new sessions. Yes, that means you'll have to disconnect/reconnect to see the change in your own session. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: trying to change wait_timeout
On 09/08/2011 02:56 AM, Johan De Meersman wrote: - Original Message - From: Bruce Ferrellbferr...@baywinds.org To: mysql@lists.mysql.com Sent: Thursday, 8 September, 2011 3:10:16 AM Subject: trying to change wait_timeout I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] That, and restart the service, of course. You *did* think of restarting the service, I trust? :-p That being said, it is also a dynamic variable, so if you didn't restart, prefer not to restart *and* are certain your config file is correct; you can also do set global wait_timeout=xxx to have it take effect immediately for all new sessions. Yes, that means you'll have to disconnect/reconnect to see the change in your own session. Good question to ask. Yes, I did restart mysql. Both before and after show variables like 'wait_time%' returns 28800. Most confusing. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: trying to change wait_timeout
Check that you're looking at the variable in the GLOBAL scope not the SESSION scope. SHOW GLOBAL VARIABLE ... Andy On Thu, Sep 8, 2011 at 11:34 AM, Bruce Ferrell bferr...@baywinds.orgwrote: On 09/08/2011 02:56 AM, Johan De Meersman wrote: - Original Message - From: Bruce Ferrellbferr...@baywinds.org** To: mysql@lists.mysql.com Sent: Thursday, 8 September, 2011 3:10:16 AM Subject: trying to change wait_timeout I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] That, and restart the service, of course. You *did* think of restarting the service, I trust? :-p That being said, it is also a dynamic variable, so if you didn't restart, prefer not to restart *and* are certain your config file is correct; you can also do set global wait_timeout=xxx to have it take effect immediately for all new sessions. Yes, that means you'll have to disconnect/reconnect to see the change in your own session. Good question to ask. Yes, I did restart mysql. Both before and after show variables like 'wait_time%' returns 28800. Most confusing. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?** unsub=eroomy...@gmail.comhttp://lists.mysql.com/mysql?unsub=eroomy...@gmail.com
Re: trying to change wait_timeout
Set the variable wait_timeout=xxx value under the mysqld section of the configuration file and restart the mysqld server. Now check show global variables like 'wait_timeout; It should be you xxx value what ever you set. On Thu, Sep 8, 2011 at 7:25 PM, Andrew Moore eroomy...@gmail.com wrote: Check that you're looking at the variable in the GLOBAL scope not the SESSION scope. SHOW GLOBAL VARIABLE ... Andy On Thu, Sep 8, 2011 at 11:34 AM, Bruce Ferrell bferr...@baywinds.org wrote: On 09/08/2011 02:56 AM, Johan De Meersman wrote: - Original Message - From: Bruce Ferrellbferr...@baywinds.org** To: mysql@lists.mysql.com Sent: Thursday, 8 September, 2011 3:10:16 AM Subject: trying to change wait_timeout I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] That, and restart the service, of course. You *did* think of restarting the service, I trust? :-p That being said, it is also a dynamic variable, so if you didn't restart, prefer not to restart *and* are certain your config file is correct; you can also do set global wait_timeout=xxx to have it take effect immediately for all new sessions. Yes, that means you'll have to disconnect/reconnect to see the change in your own session. Good question to ask. Yes, I did restart mysql. Both before and after show variables like 'wait_time%' returns 28800. Most confusing. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?** unsub=eroomy...@gmail.com http://lists.mysql.com/mysql?unsub=eroomy...@gmail.com -- Thanks Suresh Kuna MySQL DBA
trying to change wait_timeout
Hi all, I've read the documentation on MySQL for version 5.1 and it says all I have to do is to place the following: wait_timeout=xxx under [mysqld] did it and show variable like '%wait%' still show wait_timeout at 28800 as it does when I do a set global wait_timeout=10 What am I missing? Thanks in advance, Bruce Ferrell -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Query on wait_timeout
Try this out:-) Below are the steps to generate a deadlock so that the behaviour of a deadlock can be illustrated: -- 1) Create Objects for Deadlock Example USE TEMPDB CREATE TABLE dbo.foo (col1 INT) INSERT dbo.foo SELECT 1 CREATE TABLE dbo.bar (col1 INT) INSERT dbo.bar SELECT 1 -- 2) Run in first connection BEGIN TRAN UPDATE tempdb.dbo.foo SET col1 = 1 -- 3) Run in second connection BEGIN TRAN UPDATE tempdb.dbo.bar SET col1 = 1 UPDATE tempdb.dbo.foo SET col1 = 1 -- 4) Run in first connection UPDATE tempdb.dbo.bar SET col1 = 1 Connection two will be chosen as the deadlock victim On Thu, Jun 16, 2011 at 10:53 AM, Adarsh Sharma adarsh.sha...@orkash.comwrote: How we can create a deadlock manually to test this problem. Thanks Suresh Kuna wrote: Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh -- Thanks Suresh Kuna MySQL DBA
Re: Query on wait_timeout
Thanks Suresh but I find it very difficult to implement it :- Suresh Kuna wrote: Try this out:-) Below are the steps to generate a deadlock so that the behaviour of a deadlock can be illustrated: -- 1) Create Objects for Deadlock Example USE TEMPDB Is I have to create temdb database as below : create database tempdb before running the command : For running below commands , I have to create database dbo or it is something else CREATE TABLE dbo.foo (col1 INT) INSERT dbo.foo SELECT 1 CREATE TABLE dbo.bar (col1 INT) INSERT dbo.bar SELECT 1 -- 2) Run in first connection BEGIN TRAN UPDATE tempdb.dbo.foo SET col1 = 1 Don;t understand how to implement it . Is BEGIN TRAN or BEGIN TRANSACTION command -- 3) Run in second connection BEGIN TRAN UPDATE tempdb.dbo.bar SET col1 = 1 Can U explain the below and commands : UPDATE tempdb.dbo.foo SET col1 = 1 -- 4) Run in first connection UPDATE tempdb.dbo.bar SET col1 = 1 Connection two will be chosen as the deadlock victim On Thu, Jun 16, 2011 at 10:53 AM, Adarsh Sharma adarsh.sha...@orkash.com mailto:adarsh.sha...@orkash.com wrote: How we can create a deadlock manually to test this problem. Thanks Suresh Kuna wrote: Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com mailto:yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh -- Thanks Suresh Kuna MySQL DBA
RE: Query on wait_timeout
TRAN (or TRANSACTION) will apply an implicit lock on the table which remains until the TRAN is commit or rollback subsequent DML statements on that same table will be forced to wait UNTIL the TRAN is commit or rollback when the statement for the second update on the same table comes along there is a deadlock a the first TRAN has an update lock on that same table...the second statement will not execute UNTIL the first statement TRAN is either commit or rollback releasing the initial lock on that table Viel Gluck, Martin __ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Thu, 16 Jun 2011 15:21:38 +0530 From: adarsh.sha...@orkash.com To: mysql@lists.mysql.com Subject: Re: Query on wait_timeout Thanks Suresh but I find it very difficult to implement it :- Suresh Kuna wrote: Try this out:-) Below are the steps to generate a deadlock so that the behaviour of a deadlock can be illustrated: -- 1) Create Objects for Deadlock Example USE TEMPDB Is I have to create temdb database as below : create database tempdb before running the command : For running below commands , I have to create database dbo or it is something else CREATE TABLE dbo.foo (col1 INT) INSERT dbo.foo SELECT 1 CREATE TABLE dbo.bar (col1 INT) INSERT dbo.bar SELECT 1 -- 2) Run in first connection BEGIN TRAN UPDATE tempdb.dbo.foo SET col1 = 1 Don;t understand how to implement it . Is BEGIN TRAN or BEGIN TRANSACTION command -- 3) Run in second connection BEGIN TRAN UPDATE tempdb.dbo.bar SET col1 = 1 Can U explain the below and commands : UPDATE tempdb.dbo.foo SET col1 = 1 -- 4) Run in first connection UPDATE tempdb.dbo.bar SET col1 = 1 Connection two will be chosen as the deadlock victim On Thu, Jun 16, 2011 at 10:53 AM, Adarsh Sharma adarsh.sha...@orkash.com mailto:adarsh.sha...@orkash.com wrote: How we can create a deadlock manually to test this problem. Thanks Suresh Kuna wrote: Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com mailto:yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh -- Thanks Suresh Kuna MySQL DBA
Re: Query on wait_timeout
Just a little side note, The table engine needs to be InnoDB or the transaction will not have effect, The behavior may differs also according to the isolation level, That will apply a lock on all records because no where is specified, which its not very common. Regards, Claudio On Jun 16, 2011 8:05 AM, Suresh Kuna sureshkumar...@gmail.com wrote: Try this out:-) Below are the steps to generate a deadlock so that the behaviour of a deadlock can be illustrated: -- 1) Create Objects for Deadlock Example USE TEMPDB CREATE TABLE dbo.foo (col1 INT) INSERT dbo.foo SELECT 1 CREATE TABLE dbo.bar (col1 INT) INSERT dbo.bar SELECT 1 -- 2) Run in first connection BEGIN TRAN UPDATE tempdb.dbo.foo SET col1 = 1 -- 3) Run in second connection BEGIN TRAN UPDATE tempdb.dbo.bar SET col1 = 1 UPDATE tempdb.dbo.foo SET col1 = 1 -- 4) Run in first connection UPDATE tempdb.dbo.bar SET col1 = 1 Connection two will be chosen as the deadlock victim On Thu, Jun 16, 2011 at 10:53 AM, Adarsh Sharma adarsh.sha...@orkash.com wrote: How we can create a deadlock manually to test this problem. Thanks Suresh Kuna wrote: Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh -- Thanks Suresh Kuna MySQL DBA
Query on wait_timeout
Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh
Re: Query on wait_timeout
Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh -- Thanks Suresh Kuna MySQL DBA
Re: Query on wait_timeout
How we can create a deadlock manually to test this problem. Thanks Suresh Kuna wrote: Good question Yogesh, I can say the best solution is Create a deadlock and test it, you will come to know more about it. On Wed, Jun 15, 2011 at 3:38 PM, Yogesh Kore yogeshk...@gmail.com wrote: Hi, Small doubt for wait_timeout. If my wait_timeout is set for 180 seconds and if any deadlock occures and both query are waiting to execute. What wil happen in that case? 1. Do the connection will wait till deadlock is removed or 2. Connection will close after 180 seconds as both queries are ideal and waiting for each other. Thanks, Yogesh
Re: wait_timeout help
Hi Actually I don't get any idle processes listed.. but have came across such mails.. On which platform you are running mysql? I guess this might be: If Windows, the server will drop the connection probably because of 'wait_timeout' expired. For others, the mysql gets reconnected with 'reconnect flag' set to 1 in the MySQL structure... Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi To: Visolve DB Team Cc: mysql@lists.mysql.com Sent: Wednesday, November 08, 2006 11:51 AM Subject: Re: wait_timeout help Hi I set the wait_timeout in my.cnf. Sometimes it works well and there is no idle process 120 seconds time. But sometimes there are idle processes with 1900s time. What the reason can be? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi According to the VARIABLE wait_timeout [default: 28800 seconds] a running MySQL daemon clears up idle connections if their idle period wait_timeout.so the sleeping threads will be automatically cleared if the time exceeds 'wait_timeout' variable value. 'wait_timeout' variable : The number of seconds the server waits for activity on a non-interactive connection before closing it. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. 'interactive_timeout' variable's value or wait_timeout variables values -depends on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()) Thanks ViSolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi To: Visolve DB Team Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 4:12 PM Subject: Re: wait_timeout help Thanks again I have some questions that may help me explain my problem well. 1- What's this mean: mysql SHOW PROCESSLIS; +--+---+--++---+-++-+ | Id | User | Host |db | Command | Time | State | Info | +--+---+--++---+-+-++ |1 | usr | myhost:36336 | mydb | Sleep | 2587 | | NULL | | 11 | usr | myhost:36341 | mydb | Sleep | 2587 | | NULL | | 12 | usr | myhost:36348 | mydb | Sleep | 2587 | | NULL | | 3732| usr | myhost:43940 | mydb | Sleep | 2587 | | NULL | +--+---+--++---+-+-++ Are these processes idle? If yes why MySQL doesn't kill them? 2- If I set wait_timeout variable, will they be killed on that time? 3- If I set interactive_timeout, what will happen to queries that take time longer than interactive_timeout? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou
Re: wait_timeout help
Linux Redhat ASEL 4.0 On 11/8/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Actually I don't get any idle processes listed.. but have came across such mails.. On which platform you are running mysql? I guess this might be: If Windows, the server will drop the connection probably because of 'wait_timeout' expired. For others, the mysql gets reconnected with 'reconnect flag' set to 1 in the MySQL structure... Thanks ViSolve DB Team - Original Message - *From:* Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] *To:* Visolve DB Team [EMAIL PROTECTED] *Cc:* mysql@lists.mysql.com *Sent:* Wednesday, November 08, 2006 11:51 AM *Subject:* Re: wait_timeout help Hi I set the wait_timeout in my.cnf. Sometimes it works well and there is no idle process 120 seconds time. But sometimes there are idle processes with 1900s time. What the reason can be? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi According to the VARIABLE wait_timeout [default: 28800 seconds] a running MySQL daemon clears up idle connections if their idle period wait_timeout.so the sleeping threads will be automatically cleared if the time exceeds 'wait_timeout' variable value. 'wait_timeout' variable : The number of seconds the server waits for activity on a non-interactive connection before closing it. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. 'interactive_timeout' variable's value or wait_timeout variables values -depends on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()) Thanks ViSolve DB Team. - Original Message - *From:* Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] *To:* Visolve DB Team [EMAIL PROTECTED] *Cc:* mysql@lists.mysql.com *Sent:* Tuesday, November 07, 2006 4:12 PM *Subject:* Re: wait_timeout help Thanks again I have some questions that may help me explain my problem well. 1- What's this mean: mysql SHOW PROCESSLIS; +--+---+--++---+-++-+ | Id | User | Host |db | Command | Time | State | Info | +--+---+--++---+-+-++ |1 | usr | myhost:36336 | mydb | Sleep | 2587 | | NULL | | 11 | usr | myhost:36341 | mydb | Sleep | 2587 | | NULL | | 12 | usr | myhost:36348 | mydb | Sleep | 2587 | | NULL | | 3732| usr | myhost:43940 | mydb | Sleep | 2587 | | NULL | +--+---+--++---+-+-++ Are these processes idle? If yes why MySQL doesn't kill them? 2- If I set wait_timeout variable, will they be killed on that time? 3- If I set interactive_timeout, what will happen to queries that take time longer than interactive_timeout? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1 http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1 http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key
wait_timeout help
Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a
Re: wait_timeout help
On 2006-11-07 Sayed Hadi Rastgou Haghi wrote: Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? Put wait_timeout = XXX into the [mysqld] stanza of your /etc/mysql/my.cnf (or wherever your global config file is). bye, -christian- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: wait_timeout help
Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: wait_timeout help
Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a
Re: wait_timeout help
On 2006-11-07 Sayed Hadi Rastgou Haghi wrote: Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; Ah, yes, MySQL is very confusing about this special variable: You have to use interactive_timeout = XXX to change what is called wait_timeout in SHOW VARIABLES. bye, -christian- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: wait_timeout help
Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: wait_timeout help
Thanks again I have some questions that may help me explain my problem well. 1- What's this mean: mysql SHOW PROCESSLIS; +--+---+--++---+-++-+ | Id | User | Host |db | Command | Time | State | Info | +--+---+--++---+-+-++ |1 | usr | myhost:36336 | mydb | Sleep | 2587 | | NULL | | 11 | usr | myhost:36341 | mydb | Sleep | 2587 | | NULL | | 12 | usr | myhost:36348 | mydb | Sleep | 2587 | | NULL | | 3732| usr | myhost:43940 | mydb | Sleep | 2587 | | NULL | +--+---+--++---+-+-++ Are these processes idle? If yes why MySQL doesn't kill them? 2- If I set wait_timeout variable, will they be killed on that time? 3- If I set interactive_timeout, what will happen to queries that take time longer than interactive_timeout? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a
Re: wait_timeout help
Hi According to the VARIABLE wait_timeout [default: 28800 seconds] a running MySQL daemon clears up idle connections if their idle period wait_timeout.so the sleeping threads will be automatically cleared if the time exceeds 'wait_timeout' variable value. 'wait_timeout' variable : The number of seconds the server waits for activity on a non-interactive connection before closing it. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. 'interactive_timeout' variable's value or wait_timeout variables values -depends on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()) Thanks ViSolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi To: Visolve DB Team Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 4:12 PM Subject: Re: wait_timeout help Thanks again I have some questions that may help me explain my problem well. 1- What's this mean: mysql SHOW PROCESSLIS; +--+---+--++---+-++-+ | Id | User | Host |db | Command | Time | State | Info | +--+---+--++---+-+-++ |1 | usr | myhost:36336 | mydb | Sleep | 2587 | | NULL | | 11 | usr | myhost:36341 | mydb | Sleep | 2587 | | NULL | | 12 | usr | myhost:36348 | mydb | Sleep | 2587 | | NULL | | 3732| usr | myhost:43940 | mydb | Sleep | 2587 | | NULL | +--+---+--++---+-+-++ Are these processes idle? If yes why MySQL doesn't kill them? 2- If I set wait_timeout variable, will they be killed on that time? 3- If I set interactive_timeout, what will happen to queries that take time longer than interactive_timeout? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a
Re: wait_timeout help
Hi I set the wait_timeout in my.cnf. Sometimes it works well and there is no idle process 120 seconds time. But sometimes there are idle processes with 1900s time. What the reason can be? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi According to the VARIABLE wait_timeout [default: 28800 seconds] a running MySQL daemon clears up idle connections if their idle period wait_timeout.so the sleeping threads will be automatically cleared if the time exceeds 'wait_timeout' variable value. 'wait_timeout' variable : The number of seconds the server waits for activity on a non-interactive connection before closing it. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. 'interactive_timeout' variable's value or wait_timeout variables values -depends on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()) Thanks ViSolve DB Team. - Original Message - *From:* Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] *To:* Visolve DB Team [EMAIL PROTECTED] *Cc:* mysql@lists.mysql.com *Sent:* Tuesday, November 07, 2006 4:12 PM *Subject:* Re: wait_timeout help Thanks again I have some questions that may help me explain my problem well. 1- What's this mean: mysql SHOW PROCESSLIS; +--+---+--++---+-++-+ | Id | User | Host |db | Command | Time | State | Info | +--+---+--++---+-+-++ |1 | usr | myhost:36336 | mydb | Sleep | 2587 | | NULL | | 11 | usr | myhost:36341 | mydb | Sleep | 2587 | | NULL | | 12 | usr | myhost:36348 | mydb | Sleep | 2587 | | NULL | | 3732| usr | myhost:43940 | mydb | Sleep | 2587 | | NULL | +--+---+--++---+-+-++ Are these processes idle? If yes why MySQL doesn't kill them? 2- If I set wait_timeout variable, will they be killed on that time? 3- If I set interactive_timeout, what will happen to queries that take time longer than interactive_timeout? On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi Try command line option, like mysql set @@session.wait_timeout=15; mysql show variables; Thanks Visolve DB Team. - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: Visolve DB Team [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 3:21 PM Subject: Re: wait_timeout help Thanks But this sets. GLOBAL wait_timeout variable. Cab be seen by SHOW GLOBAL VARIABLES not by SHOW VARIABLES; On 11/7/06, Visolve DB Team [EMAIL PROTECTED] wrote: Hi specify it in the .cnf file in the mysqld options: wait_timeout=x or specify it at the command line : set wait_timeout=x or start mysqld with --wait_timeout=x along with other options. Thanks ViSolve DB Team - Original Message - From: Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Tuesday, November 07, 2006 2:08 PM Subject: wait_timeout help Dear All, I want to set wait_timeout variable on mysqld startup. Is there any way to do that? -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1http://www.spreadfirefox.com/?q=affiliatesid=0t=1 Get FireFox! /a -- Sincerely, Hadi Rastgou A Google Account is the key that unlocks the world of Google. a href= http://www.spreadfirefox.com/?q=affiliatesamp;id=0amp;t=1; Get FireFox! /a
wait_timeout
I have the following in the mysqld section of my.cnf: set-variable = wait_timeout=360 everything else in the conf file seems to take but my wait_timeout variable stays at the default of 28800 my version is 4.0.20 for apple-darwin6.8 Any thoughts?
Re: wait_timeout
Hello. Set the interactive_timeout variable to this value. I recommend you to upgrade to the latest release (4.1.11 now). I have the following in the mysqld section of my.cnf: set-variable = wait_timeout=360 everything else in the conf file seems to take but my wait_timeout variable stays at the default of 28800 my version is 4.0.20 for apple-darwin6.8 Any thoughts? Rob Brooks [EMAIL PROTECTED] wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Possible bug with wait_timeout
Hello. The value of wait_timeout is initialized from wait_timeout variable or from the global interactive_timeout variable, depending on the type of client. Put interactive_timeout=10 in your config file. See: http://dev.mysql.com/doc/mysql/en/Server_system_variables.html Andrew Braithwaite [EMAIL PROTECTED] wrote: Hi all, In version 4.0.18 when setting the wait_timeout variable to 10 in my.cnf, it seems to work when looking at 'mysqladmin variables' as it is indeed showing up as 10. However, when in the mysql client and I do a 'show variables' it is showing up with the default value of 28800. I'm certain that I've connected to the same server and was using all the tools from /usr/bin/mysql and specifying paths like this bin/safe_mysqld, bin/mysqladmin, bin/mysql etc... Anyone seen this before or am I going crazy? Cheers, Andrew query, sql -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Possible bug with wait_timeout
Hi all, In version 4.0.18 when setting the wait_timeout variable to 10 in my.cnf, it seems to work when looking at 'mysqladmin variables' as it is indeed showing up as 10. However, when in the mysql client and I do a 'show variables' it is showing up with the default value of 28800. I'm certain that I've connected to the same server and was using all the tools from /usr/bin/mysql and specifying paths like this bin/safe_mysqld, bin/mysqladmin, bin/mysql etc... Anyone seen this before or am I going crazy? Cheers, Andrew query, sql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.0.18/Dual AMD64 thread zombie even when wait_timeout is set to 60 seconds! Bug?
Hi guys, We have a problem with Dual AMD64 Opteron/MySQL 4.0.18/Mandrake 10 for a very high volume site. We are evaluating the performance on our new server AMD64 and it seems it's slow compared to Dual Xeon/MySQL 4.0.15/RedHat8 and Dual Xeon/MySQL 4.0.18/Mandrake 10. And it seems there are zombie threads. 570 threads in 1 hour and we didn't even use JDBC connection pooling at all. These threads are supposed to be gone within 60 seconds, since we set that option in mysqld. Note that we run many SELECT queries (can be up to 150 queries/seconds), but the system does not indicate any slow query: it's 0! Our configuration is Apache 2.0.48 + Tomcat 5.0.27 + MySQL 4.0.18 with MySQL connector/J 3.0.14 (latest stable). The Redhat 8 runs on Apache 2 + Tomcat 4.0 + MySQL 4.0.15. The old Redhat 8 on Xeon was fine. We have another machine running Mandrake 10 on Xeon and they were fine under the same load. I have set the wait_timeout to 60 seconds, and it appears to be fine within 10 minutes, all the threads that are in sleep mode disappeared after 60 seconds. After a few minutes though, it's back like it was before. Is this Mandrake problem? MySQL problem? I read in here than Mandrake win hands down on AMD64 compared to FreeBSD. http://news.gw.com/freebsd.amd64/1030 What do you think cause this problem on MySQL/AMD64? Is there such problem in v4.0.18? Thanks, Prana Here's the info: === This MySQL server has been running for 0 days, 1 hours, 20 minutes and 48 seconds. It started up on Aug 26, 2004 at 11:24 PM. === Query statistics: Since its startup, 261,670 queries have been sent to the server. Total ø per hour ø per minute ø per second 261,670 194,309.41 3,238.49 53.97 === Uptime: 5559 Threads: 569 Questions: 261705 Slow queries: 0 Opens: 74 Flush tables: 1 Open tables: 68 Queries per second avg: 47.078 === Mandrake Packages: MySQL-common-4.0.18-1.1.100mdk lib64mysql12-4.0.18-1.1.100mdk perl-Mysql-1.22_19-9mdk MySQL-4.0.18-1.1.100mdk MySQL-client-4.0.18-1.1.100mdk php-mysql-4.3.4-1mdk [EMAIL PROTECTED] root]# mysql -e 'show variables like %time%' +--+---+ | Variable_name| Value | +--+---+ | connect_timeout | 5 | | delayed_insert_timeout | 300 | | flush_time | 0 | | innodb_lock_wait_timeout | 50| | interactive_timeout | 60| | long_query_time | 10| | net_read_timeout | 30| | net_write_timeout| 60| | slave_net_timeout| 3600 | | slow_launch_time | 2 | | timezone | SGT | | wait_timeout | 30| +--+---+ [my.cnf]== [client] port= 3306 socket = /var/lib/mysql/mysql.sock [mysqld] wait_timeout=30 interactive_timeout=60 port= 3306 socket = /var/lib/mysql/mysql.sock skip-locking log-slow-queries key_buffer = 384M max_allowed_packet = 1M table_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M myisam_sort_buffer_size = 64M thread_cache = 128 query_cache_size = 32M max_connections=1200 thread_concurrency = 4 connect_timeout = 5 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout == Prana -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Session wait_timeout and interactive_timeout variables
Do the following commands, when run from an already-established connection, actually have any bearing on anything? SET SESSION wait_timeout=10; SET SESSION interactive_timeout=10; I am working on an application using the C API that needs to lock tables while doing updates. This works fine except for in the rare case when the computer the application is running on loses connectivity while a table is locked. Normally this wouldn't be a huge deal, but I am concerned because the application will mostly be running over a wireless connection which is of course subject to loss of signal. So if one person running the application loses his signal, no one else will be able to do anything. The problem I'm running into is this - I'm testing out this situation by running the mysql command-line client on one computer, write-locking a table, starting a select query from that table on another machine, and turning off the wireless to the first machine. The second machine continues to hang as the mysql server doesn't kill the connection to the first machine and thus its lock is still in effect. Now I believe that wait_timeout and/or interactive_timeout are what I need to help me out by killing such dead threads and thus setting a maximum time that others could hang. This is all well and great, but I am not the admin of the server, so I can't set them globally and the default values of 8 hours are obviously unreasonable for me. In the testing sequence described above, I tried running SET SESSION wait_timeout=10; SET SESSION interactive_timeout=10; on the first machine before acquiring the lock and turning off wireless, but it seemed to have no effect as the second machine continued to hang for the seven minutes I let it sit. After setting the session variables I tried checking them with a select statement, and they showed 10 seconds like they should. It just seems like the server doesn't actually honor them. Is there a problem with the server here, or am I just misunderstanding the way session variables are intended to work? Or is the way I am simulating this case flawed? I must say that the documentation is not very verbose about server variables and so wasn't extremely helpful to me in solving this problem. If there's another better way to solve my locking issue, I would love to hear that as well. Thanks, Aaron Jacobs [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
wait_timeout
The manual describes wait_timeout thusly: The number of seconds the server waits for activity on a non-interactive connection before closing it. On thread startup, the session wait_timeout value is initialized from the global wait_timeout value or from the global interactive_timeout value, depending on the type of client (as defined by the CLIENT_INTERACTIVE connect option to mysql_real_connect()). See also interactive_timeout. What is defined as 'activity'? For example, if the client connection issues a query which requires 6 minutes for the server to process, will it timeout with a wait_timeout of 5m, or does wait_timeout understand that the query has not yet been completed?
Re: set wait_timeout
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hi, i have problem with automatic setting of variable wait_timeout. mysql version 4.0.20 (and 4.0.18) on slackware linux. i've tried to set it in several ways: 1) in startup script as a parameter to mysql_safe: -O wait_timeout=30 2a) in configuration file /etc/my.cnf, section [mysqld]: set-variable=wait_timeout=30 2b) in configuration file /etc/my.cnf, section [mysqld]: wait_timeout=30 3) from the shell (i've planed to place it into the startup script after mysqld_safe start): mysql -e 'set wait_timeout=30' nothing worked, i got no error message and the value of wait_timeout stood default: 28800. when i run 'set wait_timeout=30;' as privileged user in interactive mysql session (running 'mysql'), the value changes as i wish. what should i do to set the variable at startup? If you check wait_timeout value using mysql command-line client, it takes value for 'wait_timeout' from 'interactive_timeout' variable which is 28800 by default. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
[Re: Re: set wait_timeout]
If you check wait_timeout value using mysql command-line client, it takes value for 'wait_timeout' from 'interactive_timeout' variable which is 28800 by default. thanks, now i see. this behaviour is rather strange, isn't it? why are there two different variables then? i thought that wait_timeout is for non-interactive and interactive_timeout for interactive clients. when i run: mysql -e 'show variables;' then i get right value (=30), as i set it on startup. when i start mysql command line client and run: show variables; then i get value for interactive_timeout (it's default =28800). } this is what you pointed out. but when i run: mysql -e 'set wait_timeout=26600;' mysql -e 'show variables;' then i get old values: wait_timeout=30 interactive_timeout=28800 this behaviour is quite odd and i don't see a way how to set wait_timeout for non-interactive clients from interactive session. (i suppose that mysql command line client is non-interactive when it runs with the -e parameter) rudolf -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: [Re: Re: set wait_timeout]
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: If you check wait_timeout value using mysql command-line client, it takes value for 'wait_timeout' from 'interactive_timeout' variable which is 28800 by default. thanks, now i see. this behaviour is rather strange, isn't it? why are there two different variables then? i thought that wait_timeout is for non-interactive and interactive_timeout for interactive clients. when i run: mysql -e 'show variables;' then i get right value (=30), as i set it on startup. when i start mysql command line client and run: show variables; then i get value for interactive_timeout (it's default =28800). } this is what you pointed out. but when i run: mysql -e 'set wait_timeout=26600;' mysql -e 'show variables;' then i get old values: wait_timeout=30 interactive_timeout=28800 Because you set session variable and SHOW VARIABLES display values for global variables. Use GLOBAL keyword in the SET statement. shell mysql -e SET @@GLOBAL.wait_timeout=26600 this behaviour is quite odd and i don't see a way how to set wait_timeout for non-interactive clients from interactive session. (i suppose that mysql command line client is non-interactive when it runs with the -e parameter) -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
set wait_timeout
hi, i have problem with automatic setting of variable wait_timeout. mysql version 4.0.20 (and 4.0.18) on slackware linux. i've tried to set it in several ways: 1) in startup script as a parameter to mysql_safe: -O wait_timeout=30 2a) in configuration file /etc/my.cnf, section [mysqld]: set-variable=wait_timeout=30 2b) in configuration file /etc/my.cnf, section [mysqld]: wait_timeout=30 3) from the shell (i've planed to place it into the startup script after mysqld_safe start): mysql -e 'set wait_timeout=30' nothing worked, i got no error message and the value of wait_timeout stood default: 28800. when i run 'set wait_timeout=30;' as privileged user in interactive mysql session (running 'mysql'), the value changes as i wish. what should i do to set the variable at startup? thanks, rudolf -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: disabling wait_timeout?
Neale Banks said: Can it be done? I tried to disable this timer with wait_timeout = 0 in my.cnf. That changed the timeout (as reported by mysqladmin variables) from the default 28800 to 1. Tested, it was definitely a one-second timeout :-( As a hack-around, I've currently got it set to ten days. Alternatively, where is the bounds for the value of wait_timeout documented? Lastly, this is for a long-held JDBC connection from an application server which could run for days, no, weeks - and gets upset if mysql closes down the connection (e.g. overnight/weekends). Any suggestions on a better way to handle this? Neale, JDBC connections aren't guaranteed to last forever (I even checked with the JDBC spec lead on this). You need to make sure your application has the 'smarts' to handle connection failure, and re-connect and retry the transaction (if it makes sense), or mark the current connection as bad, pass the exception up the stack, and re-establish the connection later. Connections don't go away just because of wait_timeout, someone might unplug a switch, restart the database server, ifconfig an interface down, router flakes out...There are many potential failure scenarios for a network connection, and only your application will know what the _prudent_ action to take (retry immediately, throw error retry later, shutdown, etc0 is. Luckily, most application servers' connection pools have parameters you can configure to expire connections that have been idle too long, test connections while they are idle to see that they are still valid, test connections before handing them out, or when getting them returned, etc., etc. Regards, -Mark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
disabling wait_timeout?
Can it be done? I tried to disable this timer with wait_timeout = 0 in my.cnf. That changed the timeout (as reported by mysqladmin variables) from the default 28800 to 1. Tested, it was definitely a one-second timeout :-( As a hack-around, I've currently got it set to ten days. Alternatively, where is the bounds for the value of wait_timeout documented? Lastly, this is for a long-held JDBC connection from an application server which could run for days, no, weeks - and gets upset if mysql closes down the connection (e.g. overnight/weekends). Any suggestions on a better way to handle this? Thanks, Neale. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Setting wait_timeout in my.cnf?
Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Setting wait_timeout in my.cnf?
correction: section shoud be read as [mysqld] -Original Message- From: Hoeven, Maarten van der Sent: Tuesday, November 11, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Setting wait_timeout in my.cnf? Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Setting wait_timeout in my.cnf?
Hi Maarten, I havent tried it recently but substitute any underbar (_) with a hiven (-) when doing a setting in the my.cnf. -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 20:22, Hoeven, Maarten van der wrote: correction: section shoud be read as [mysqld] -Original Message- From: Hoeven, Maarten van der Sent: Tuesday, November 11, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Setting wait_timeout in my.cnf? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html --- -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Re: Setting wait_timeout in my.cnf?
nope, that didnt help. Thanks though! Any other suggestions? -Original Message- From: Nils Valentin [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 1:00 PM To: [EMAIL PROTECTED] Subject: Re: Setting wait_timeout in my.cnf? Hi Maarten, I havent tried it recently but substitute any underbar (_) with a hiven (-) when doing a setting in the my.cnf. -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 20:22, Hoeven, Maarten van der wrote: correction: section shoud be read as [mysqld] -Original Message- From: Hoeven, Maarten van der Sent: Tuesday, November 11, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Setting wait_timeout in my.cnf? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html --- -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Setting wait_timeout in my.cnf?
Hmm. You could try show variables like %timeout%; perhaps interactive_timeout can help you out ? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 21:37, Hoeven, Maarten van der wrote: nope, that didnt help. Thanks though! Any other suggestions? -Original Message- From: Nils Valentin [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 1:00 PM To: [EMAIL PROTECTED] Subject: Re: Setting wait_timeout in my.cnf? Hi Maarten, I havent tried it recently but substitute any underbar (_) with a hiven (-) when doing a setting in the my.cnf. -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 20:22, Hoeven, Maarten van der wrote: correction: section shoud be read as [mysqld] -Original Message- From: Hoeven, Maarten van der Sent: Tuesday, November 11, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Setting wait_timeout in my.cnf? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html --- -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Setting wait_timeout in my.cnf?
Hoeven, Maarten van der [EMAIL PROTECTED] wrote: gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. Set up value for interactive_timeout variable, too. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Setting wait_timeout in my.cnf?
tsss, how about that :) yes, I can set interactive_timeout to a value in my.cnf (interactive_timeout=30). This works! However, as a side-effect, wait_timeout is *also* set to 30. Right, problem solved. Thanks, Nils. Maarten -Original Message- From: Nils Valentin [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 1:48 PM To: [EMAIL PROTECTED] Cc: Hoeven, Maarten van der Subject: Re: Setting wait_timeout in my.cnf? Hmm. You could try show variables like %timeout%; perhaps interactive_timeout can help you out ? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 21:37, Hoeven, Maarten van der wrote: nope, that didnt help. Thanks though! Any other suggestions? -Original Message- From: Nils Valentin [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 1:00 PM To: [EMAIL PROTECTED] Subject: Re: Setting wait_timeout in my.cnf? Hi Maarten, I havent tried it recently but substitute any underbar (_) with a hiven (-) when doing a setting in the my.cnf. -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ On Tuesday 11 November 2003 20:22, Hoeven, Maarten van der wrote: correction: section shoud be read as [mysqld] -Original Message- From: Hoeven, Maarten van der Sent: Tuesday, November 11, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Setting wait_timeout in my.cnf? -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ Hi all, gosh, I must be overlooking something obvious. Running mysql 4.0.16. I want to set the wait_timeout in my.cnf (section [mysql]) like: wait_timeout = 300 also tried the depricated set-variable = wait_timeout=300 Both are not working; still default to 28800. Sure, I stopped and started the server. However, when I set the variable in the mysql-client with: set wait_timeout=30; the variable wait_timeout is changed! What am I overlooking? I really want to set this in my config-file, rather that setting it manually in the client... Any hints? PS. Linux Redhat 9 out of the Box, kernel 2.4.20-8 Maarten -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html --- -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/ -- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Quick query on 'wait_timeout' parameter.
Hi, I have many Mysql connection threads sleeping which is taking a very good amount of memory so I am reducing 'wait_timeout' parameter from default 8 Hr to 1Hr. Will it have any side effects on My web application. I am concerned because I don't know why the default was kept so high as to 8Hr. Any help will be appreciated .. Thanks and Regards, Shailesh Agrawal -- For sale, parachute, used once, never opened, small stain.
setting the wait_timeout option - doesn't work?
Hey All-- I have MySQL 4.0.14 running on Redhat Linux and it won't accept my change to the wait_timeout config option! In the my.cnf file I have a line wait_timeout = 60 but when I restart mysql and go into the server and type SHOW VARIABLES; it says the wait_timeout is still 28800 which is too long! Any ideas? Thanks, Matt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: setting the wait_timeout option - doesn't work?
On Thu, Oct 02, 2003 at 02:02:34PM -0400, Matt Babineau wrote: Hey All-- I have MySQL 4.0.14 running on Redhat Linux and it won't accept my change to the wait_timeout config option! In the my.cnf file I have a line wait_timeout = 60 but when I restart mysql and go into the server and type SHOW VARIABLES; it says the wait_timeout is still 28800 which is too long! Are you sure MySQL is reading the my.cnf file? Is the setting in the correct ([mysqld]) section? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 18 days, processed 682,784,147 queries (417/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: setting the wait_timeout option - doesn't work?
Yeah mysql is reading the config file, because I have set other options like query_cache_size...so I'm not sure :-( On Thu, 2003-10-02 at 18:09, Jeremy Zawodny wrote: On Thu, Oct 02, 2003 at 02:02:34PM -0400, Matt Babineau wrote: Hey All-- I have MySQL 4.0.14 running on Redhat Linux and it won't accept my change to the wait_timeout config option! In the my.cnf file I have a line wait_timeout = 60 but when I restart mysql and go into the server and type SHOW VARIABLES; it says the wait_timeout is still 28800 which is too long! Are you sure MySQL is reading the my.cnf file? Is the setting in the correct ([mysqld]) section? Jeremy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: setting the wait_timeout option - doesn't work?
At 14:02 2/10/2003 -0400, Matt Babineau wrote: Hi, cut it says the wait_timeout is still 28800 which is too long! Any ideas? mysql show variables like wait_timeout; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 28800 | +---+---+ 1 row in set (0.00 sec) mysql SET @@WAIT_TIMEOUT=60; Query OK, 0 rows affected (0.00 sec) mysql show variables like wait_timeout; +---+---+ | Variable_name | Value | +---+---+ | wait_timeout | 60| +---+---+ 1 row in set (0.00 sec) -- Regards, For technical support contracts, visit https://order.mysql.com/ Are you MySQL certified?, http://www.mysql.com/certification/ Miguel Angel Solórzano [EMAIL PROTECTED] São Paulo - Brazil --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.516 / Virus Database: 313 - Release Date: 1/9/2003 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: WG: wait_timeout in my.cnf
On Wednesday 16 July 2003 16:10, Moritz Steiner wrote: Like this: # The number of seconds the server waits for activity on a connection # before closing it wait_timeout= 300 Set interactive_timeout=300, too. -Urspr?ngliche Nachricht- Von: Egor Egorov [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. Juli 2003 09:55 An: [EMAIL PROTECTED] Betreff: Re: WG: wait_timeout in my.cnf Moritz Steiner [EMAIL PROTECTED] wrote: I set a lot of variables in the my.cnf file, all variables are set (I checked it with show variables) except of wait_timeout. If I set the option in MySQL with option wait_status=xxx it works. How did you set the wait_timeout variable? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
AW: WG: wait_timeout in my.cnf
Thanks a lot, that solved my problem! Moritz -Ursprüngliche Nachricht- Von: Egor Egorov [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 18. Juli 2003 10:16 An: [EMAIL PROTECTED] Betreff: Re: WG: wait_timeout in my.cnf On Wednesday 16 July 2003 16:10, Moritz Steiner wrote: Like this: # The number of seconds the server waits for activity on a connection # before closing it wait_timeout= 300 Set interactive_timeout=300, too. -Urspr?ngliche Nachricht- Von: Egor Egorov [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. Juli 2003 09:55 An: [EMAIL PROTECTED] Betreff: Re: WG: wait_timeout in my.cnf Moritz Steiner [EMAIL PROTECTED] wrote: I set a lot of variables in the my.cnf file, all variables are set (I checked it with show variables) except of wait_timeout. If I set the option in MySQL with option wait_status=xxx it works. How did you set the wait_timeout variable? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: WG: wait_timeout in my.cnf
Moritz Steiner [EMAIL PROTECTED] wrote: I set a lot of variables in the my.cnf file, all variables are set (I checked it with show variables) except of wait_timeout. If I set the option in MySQL with option wait_status=xxx it works. How did you set the wait_timeout variable? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
WG: wait_timeout in my.cnf
I set a lot of variables in the my.cnf file, all variables are set (I checked it with show variables) except of wait_timeout. If I set the option in MySQL with option wait_status=xxx it works. Does anybody know why this could happen? Thanks, Moritz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problems with JDBC autoReconnect and wait_timeout
Hi, I am having major problems with persistant database connections on a resident process in java. My database connection url looks like this: jdbc:mysql://balti/log?autoReconnect=trueuser=rootpassword=pineapple But it does not appear to be reconnecting because if I go into /etc/my.cnf and set variable wait_timout to be 3 seconds or so I get the usual java Communication Link exception, meaning the the connection has gone idle and no attempt has been made to reconnect. the version I am using is mysql-connector-java-3.0.6-stable. Another curious factor is that the wait_timout applies to my java connections but not when I run mysql as root. Why is this? The mysql version is mysql-max-4.0.9-gamma-pc-linux-i686 The most disturbing thing is that the url autoReconnect seems to not be working. Emma. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems with JDBC autoReconnect and wait_timeout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Emma Wansbrough wrote: Hi, I am having major problems with persistant database connections on a resident process in java. My database connection url looks like this: jdbc:mysql://balti/log?autoReconnect=trueuser=rootpassword=pineapple But it does not appear to be reconnecting because if I go into /etc/my.cnf and set variable wait_timout to be 3 seconds or so I get the usual java Communication Link exception, meaning the the connection has gone idle and no attempt has been made to reconnect. the version I am using is mysql-connector-java-3.0.6-stable. Another curious factor is that the wait_timout applies to my java connections but not when I run mysql as root. Why is this? The mysql version is mysql-max-4.0.9-gamma-pc-linux-i686 The most disturbing thing is that the url autoReconnect seems to not be working. Emma. Have you read the README that comes with Connector/J 3.0.6? The autoReconnect behavior has changed: Fail-over only happens when the connection is in a autoCommit(true) state, because fail-over can not happen reliably when a transaction is in progress. Most good application servers and connection pools set autoCommit to 'true' at the end of every transaction/connection use. -Mark - -- MySQL 2003 Users Conference - http://www.mysql.com/events/uc2003/ For technical support contracts, visit https://order.mysql.com/?ref=mmma __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Mark Matthews [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java /_/ /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA ___/ www.mysql.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.1.90 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+bj5ptvXNTca6JD8RAmXHAKCrKByD3CVmmbHvF/FA0EL+r11bywCfYj4b fZp6fi41h0NNlm4b5CtJIzo= =Sext -END PGP SIGNATURE- - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
wait_timeout doesnt get set
Hi It seems I cannot set wait_timeout variable. I set it up in /etc/my.cnf with this line: set-variable= wait_timeout=15 under [mysqld] section. I tried MySQL 3.23.48 and 3.23.49a (binary, linux i686 distributions, we cannot use newer ones as they have serious problems under heavy load). When I do mysql --help at the end it will give me a list of default values, in which it will show wait_timeout as 15 (as set in my.cnf) but when I do show variables on mysql console it shows wait_timeout as 30. This is very strange as I run exactly the same config (3.23.48) on another server and there it shows wait_timeout as set in my.cnf. Where else should I look ? Thanks Mihai RUSU Disclaimer: Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of any company, unless otherwise specifically stated. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
wait_timeout
Greeting to all. Here is some data on my server : [student:99] /usr/local/bin mysqladmin -u root -p version 9:18 Enter password: *** mysqladmin Ver 8.23 Distrib 3.23.52, for hp-hpux11.00 on hppa2.0w Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.52-log Protocol version10 Connection Localhost via UNIX socket UNIX socket /student1/mysql/mysql.sock Uptime: 6 min 31 sec Threads: 1 Questions: 8 Slow queries: 0 Opens: 7 Flush tables: 1 Open tables: 1 Queries per second avg: 0.020 [student:100] /usr/local/bin 9:18 I am writing a unix deamon for email processing that uses this mysql server. I got a MySQL error: MySQL server has gone away error. I figured the reason was that my connection timed out. This was because my deamon opens the connections it needs at startup and uses them throughout its lifetime, thus causing gone away error. I saw 2 fixes for this. 1. Increasing wait_timeout value. How should i do this so that it is set to the new value every time i start the server? 2. Opening and closing a mysql connection each time I need to execute a query. Is this a good way to do things, or should I prefer the above method? One more question. I moved mysql.sock file from /tmp to protect it from beeing deleted by admins when system is cleanedup. It is now located in /student1/mysql/ directory. I changed all relevant paths in /etc/my.cnf file but still when I issue `mysql` on the command line it complaints about beeing unable to find /tmp/mysql.sock, only mysql --socket=/student1/mysql/mysql.sock works. Why? Here is my.cnf : # Example mysql config file for medium systems. # # This is for a system with little memory (32M - 64M) where MySQL plays # a important part and systems up to 128M very MySQL is used together with # other programs (like a web server) # # You can copy this file to # /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is /usr/local/mysql/var) or # ~/.my.cnf to set user-specific options. # # One can in this file use all long options that the program supports. # If you want to know which options a program support, run the program # with --help option. # The following options will be passed to all MySQL clients [client] #password = your_password port= 3306 socket = /student1/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port= 3306 socket = /student1/mysql/mysql.sock skip-locking set-variable= key_buffer=16M set-variable= max_allowed_packet=1M set-variable= table_cache=64 set-variable= sort_buffer=512K set-variable= net_buffer_length=8K set-variable= myisam_sort_buffer_size=8M log-bin server-id = 1 # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using BDB tables #set-variable = bdb_cache_size=4M #set-variable = bdb_max_lock=1 # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /usr/local/mysql/var/ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = /usr/local/mysql/var/ #innodb_log_arch_dir = /usr/local/mysql/var/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #set-variable = innodb_buffer_pool_size=16M #set-variable = innodb_additional_mem_pool_size=2M # Set .._log_file_size to 25 % of buffer pool size #set-variable = innodb_log_file_size=5M #set-variable = innodb_log_buffer_size=8M #innodb_flush_log_at_trx_commit=1 #set-variable = innodb_lock_wait_timeout=50 [mysqldump] quick set-variable= max_allowed_packet=16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] set-variable= key_buffer=20M set-variable= sort_buffer=20M set-variable= read_buffer=2M set-variable= write_buffer=2M [myisamchk] set-variable= key_buffer=20M set-variable= sort_buffer=20M set-variable= read_buffer=2M set-variable= write_buffer=2M [mysqlhotcopy] interactive-timeout Thank you for any and all help, and I loved mysql so far. Vlatko - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: max_connect_errors wait_timeout problem?
On Wed, 2002-07-31 at 19:09, Troy Hakala wrote: I decreased wait_timeout (from 28,800 to 300) to kill off sleeping threads. This morning, the server stopped accepting connections and gave me this error: ERROR 1129: Host 'hostname' is blocked because of many connection errors. Unblock with 'mysqladmin flush-hosts' flush-hosts worked and I increased the max_connect_errors from 10 to 1000 to kind of prevent this in the future. But what causes this error? If you read the comments on http://www.mysql.com/doc/B/l/Blocked_host.html it seems that decreasing wait_timeout does cause this. Is there a bug in mysql where it thinks that killing off sleeping threads is really a connect error? I'm using 3.23.45, btw. I'm not shure, but i think it is not a bug. I think a connection is only successfull when it is closed by the same entity who opened it. If it was mysql closing the connection, then it should increment its counter of connection_errors. It tells that someone opened a connection and did not close it. It's only an opinion. -- Diana Soares - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
max_connect_errors wait_timeout problem?
I decreased wait_timeout (from 28,800 to 300) to kill off sleeping threads. This morning, the server stopped accepting connections and gave me this error: ERROR 1129: Host 'hostname' is blocked because of many connection errors. Unblock with 'mysqladmin flush-hosts' flush-hosts worked and I increased the max_connect_errors from 10 to 1000 to kind of prevent this in the future. But what causes this error? If you read the comments on http://www.mysql.com/doc/B/l/Blocked_host.html it seems that decreasing wait_timeout does cause this. Is there a bug in mysql where it thinks that killing off sleeping threads is really a connect error? I'm using 3.23.45, btw. Thanks! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Server Config wait_timeout
Hi, I've started mysql with the parameter -O wait_timeout=1000 and verified that it is set using show variables. Yet I routinely see lingering processes with times over 1100 and higher. I have about 1000 active database users at the moment, most are connecting via php pages and I had been running out of connections. I could have increased the number of connections, but I chose rather to lower the wait_timeout instead. Should I be expecting timeouts in excess of 100 seconds beyond the value that I set?That is, is wait_timeout more of a guideline than a hard limit? Regards, Gary SuperID Huntress === FreeSQL.org offering free database hosting to developers Visit http://www.freesql.org - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
problems changing wait_timeout and interactive_timeout with Mysql-Max
Hi, I currently upgraded to Mysql-Max 3.23.38 and adapted my my.cnf file. I had a varibale setting set-variable= wait_timeout=3600 in it, but this makes the upgraded server crash on startup. Without giving any of the variables wait_timeout or interactive_timeout, the startup works fine. The last server we used (version was 3.23.14) worked fine also. We are running a PIII-dual750-1GBmemory DB Server, my settings are below. Did anybody have similar problems? best regards Markus [client] #password = your_password port= 3306 socket = /var/lib/mysql/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] port= 3306 #socket = /tmp/mysql.sock socket = /var/lib/mysql/mysql.sock exit-info safe-mode skip-delay-key-write skip-locking set-variable= back_log=99 # set-variable= interactive_timeout=3600 ### 60 minutes of inactivity is enough # set-variable= wait_timeout=3600 ### 60 minutes of inactivity is eno ugh set-variable= key_buffer_size=384M ### default cmdline was 256M set-variable= max_allowed_packet=1M set-variable= table_cache=512 ### default cmdline was 256 set-variable= tmp_table_size=32M set-variable= sort_buffer=12M ### default cmdline was 12M set-variable= record_buffer=4M ### default cmdline was 4M set-variable= thread_cache=8 set-variable= thread_concurrency=4 # Try number of CPU's*2 set-variable= myisam_sort_buffer_size=64M #log-update server-id = 1 set-variable= max_connections=200 set-variable= max_connect_errors=50 # Uncomment the following if you are using BDB tables set-variable= bdb_cache_size=384M set-variable= bdb_max_lock=10 # Uncomment the following if you are using Innobase tables #innodb_data_home_dir = /var/lib/mysql/ #innodb_log_group_home_dir = /var/lib/mysql/ #innodb_log_arch_dir = /var/lib/mysql/ #innodb_data_file_path = ibdata1:500M;ibdata2:500M;ibdata3:500M #set-variable = innodb_mirrored_log_groups=1 #set-variable = innodb_log_files_in_group=3 #set-variable = innodb_log_file_size=5M #set-variable = innodb_log_buffer_size=8M #innodb_flush_log_at_trx_commit=1 #innodb_log_archive=0 #set-variable = innodb_buffer_pool_size=256M #set-variable = innodb_additional_mem_pool_size=64M #set-variable = innodb_file_io_threads=4 #set-variable = innodb_lock_wait_timeout=30 # Point the following paths to different dedicated disks tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname [mysqldump] ... - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail mysql-unsubscribe-##L=##[EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: problems changing wait_timeout and interactive_timeout with Mysql-Max
Markus Schranz writes:
Hi,
I currently upgraded to Mysql-Max 3.23.38 and adapted my my.cnf file.
I had a varibale setting
set-variable= wait_timeout=3600
in it, but this makes the upgraded server crash on startup. Without giving
any of the
variables wait_timeout or interactive_timeout, the startup works fine. The
last server we used
(version was 3.23.14) worked fine also.
We are running a PIII-dual750-1GBmemory DB Server, my settings are below.
Did anybody have similar problems?
best regards
Markus
Hi!
Did you use our binary ??
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: wait_timeout?
On Tue, Jan 30, 2001 at 12:26:34PM -0600, Meyer, Patrick wrote: I am slowly gaining connections to the database that just sleep. I know these can arise from not closing the database. I am accessing it via MyODBC from Active Server Pages. However, I set wait_timeout to 3600... I have some that have been there for days... just sleeping. Why doesn't MySQL disconnect them from the timeout? Maybe I just don't understand wait_timeout. That's odd. I haven't had the need to use wait_timeout, so I can't say what you should expect. But I'd expect that it should work as documented. Do they appear to have anything particular in common? Same host/user/db? Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: wait_timeout? More Info.
Primarily the database serves the web server so it is always the same host. The database may vary, but some more than others. I feel confident that some path through an ASP either crashes or the connection close command is never reached or does not exist. However, I would think that the timeout would still kill those they are sleeping... for days. BTW, I am running 2.23.32 on Win2K. I have been trying to come up with an easy way to know which ASP has the error in it. Only thing I can think of is to create dozens of usernames and use a different one in each file ick... that will take some time. [EMAIL PROTECTED] - Original Message - From: "Jeremy D. Zawodny" [EMAIL PROTECTED] To: "Meyer, Patrick" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 2:48 AM Subject: Re: wait_timeout? On Tue, Jan 30, 2001 at 12:26:34PM -0600, Meyer, Patrick wrote: I am slowly gaining connections to the database that just sleep. I know these can arise from not closing the database. I am accessing it via MyODBC from Active Server Pages. However, I set wait_timeout to 3600... I have some that have been there for days... just sleeping. Why doesn't MySQL disconnect them from the timeout? Maybe I just don't understand wait_timeout. That's odd. I haven't had the need to use wait_timeout, so I can't say what you should expect. But I'd expect that it should work as documented. Do they appear to have anything particular in common? Same host/user/db? Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: wait_timeout?
On Wed, 31 Jan 2001, Andrew Benham wrote: I'm glad it's not just me. I have 2 v3.22.32 servers running under HP-UX 10.20 Both servers are being used by FCGI processes on the web with persistant connections to the database servers. Ok, I'll join in on this. I have servers running Slackware 7.1 with v3.22.28-gamma servers (yes, I'll upgrade), and I had to let persistent connections go because of this. It seems, things are extremely sluggish as soon as I reach 100+ connections (and this is a dual PIII/700 with 1Gb RAM and my-huge.cnf) and the connections tend to stay around. Good luck with hunting it down, thou' :-) Regards, Jan-Aage -- Mr. Jan-Aage Bruvoll Managing Director Bruvoll Brains in Bits, 7a Neal's Yard, London WC2H 9DP, UK Office: +442072408283 Cell: +4792492482 Fax: +4792571158 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
wait_timeout?
I am slowly gaining connections to the database that just sleep. I know these can arise from not closing the database. I am accessing it via MyODBC from Active Server Pages. However, I set wait_timeout to 3600... I have some that have been there for days... just sleeping. Why doesn't MySQL disconnect them from the timeout? Maybe I just don't understand wait_timeout. Help appreciated. [EMAIL PROTECTED] National Aeronautics and Space Administration -- S c i e n c e @ N A S A -- http://science.nasa.gov/ INFORM - the fast paced expansion of knowledge http://kids.msfc.nasa.gov/ INSPIRE - the future belongs to our children http://liftoff.msfc.nasa.gov/ INVOLVE - today's dreams, tomorrow's reality. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
