Re: Change wait_timeout parameter
I would argue that it is the application that needs changing, not any MySQL setting.
Do you really want open connections lying around, not doing anything useful but still using up database resources for 82,966,646 milliseconds? Hint: In the Real World, that's just a touch shy of 23 hours, 3 minutes!
From the application's perspective, database connections should be opened, used [closed] and trashed as rapidly as possible, to keep things tidy (connection pooling usually takes care of the overhead of this).
Regards, Phill W.
Subject
Written By
Posted
November 29, 2011 02:46AM
Re: Change wait_timeout parameter
November 29, 2011 07:01AM
November 29, 2011 07:54AM
December 04, 2011 07:19PM
December 02, 2011 07:57AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.