<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MySQL Server Has Gone Away problem solved</title>
	<atom:link href="http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Feb 2010 13:45:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: iGuide</title>
		<link>http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/comment-page-1/#comment-1505</link>
		<dc:creator>iGuide</dc:creator>
		<pubDate>Thu, 17 Sep 2009 19:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/#comment-1505</guid>
		<description>So, what&#039;s the configuration option that needs to be changed to solve this problem?</description>
		<content:encoded><![CDATA[<p>So, what&#8217;s the configuration option that needs to be changed to solve this problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mine</title>
		<link>http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/comment-page-1/#comment-1430</link>
		<dc:creator>mine</dc:creator>
		<pubDate>Tue, 21 Oct 2008 23:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/#comment-1430</guid>
		<description>It works for me.
Thanks alot.</description>
		<content:encoded><![CDATA[<p>It works for me.<br />
Thanks alot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yo</title>
		<link>http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/comment-page-1/#comment-1328</link>
		<dc:creator>yo</dc:creator>
		<pubDate>Thu, 21 Aug 2008 14:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/#comment-1328</guid>
		<description>yo,im also on godaddy
and i must say that error (sever has gone) when running longer sql queries really pissed me off.
though,the solution seems to be to mysql_close() the connection before it exceeds the time limit what actually probably causes godaddy service to close the connection itself.
but what i just recently noticed is,
check out Mysql Proccesslist on Godaddy MYSQL Servers,
you will see the port changes,that could be one reason why it says &quot;Server gone&quot;.
so each time you close the connection and estabilish a new one it catches the new port(which could have changed in an interval of max time).
So there are 2 theories:

1.Godaddy simply set a quite short maximum of connection time. : Workarround =&gt; mysql_close();
2.Godaddy changes port in an unknown interval(would need some research to find it out). : Workarround =&gt; mysql_close();

Maybe mysql_free_ressources also can help a bit,but i dont think so(just give it a try :)

so the final solution seems to be to close the godaddy mysql connection as fast as possible.

close,connect ... probably wont cause your server to crash(not really similiar to DOS) so no worries!</description>
		<content:encoded><![CDATA[<p>yo,im also on godaddy<br />
and i must say that error (sever has gone) when running longer sql queries really pissed me off.<br />
though,the solution seems to be to mysql_close() the connection before it exceeds the time limit what actually probably causes godaddy service to close the connection itself.<br />
but what i just recently noticed is,<br />
check out Mysql Proccesslist on Godaddy MYSQL Servers,<br />
you will see the port changes,that could be one reason why it says &#8220;Server gone&#8221;.<br />
so each time you close the connection and estabilish a new one it catches the new port(which could have changed in an interval of max time).<br />
So there are 2 theories:</p>
<p>1.Godaddy simply set a quite short maximum of connection time. : Workarround =&gt; mysql_close();<br />
2.Godaddy changes port in an unknown interval(would need some research to find it out). : Workarround =&gt; mysql_close();</p>
<p>Maybe mysql_free_ressources also can help a bit,but i dont think so(just give it a try <img src='http://blog.terrypearson.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>so the final solution seems to be to close the godaddy mysql connection as fast as possible.</p>
<p>close,connect &#8230; probably wont cause your server to crash(not really similiar to DOS) so no worries!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim - 406NotAccceptable</title>
		<link>http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/comment-page-1/#comment-1067</link>
		<dc:creator>Jim - 406NotAccceptable</dc:creator>
		<pubDate>Sun, 02 Mar 2008 01:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.terrypearson.com/2008/02/29/mysql-server-has-gone-away-problem-solved/#comment-1067</guid>
		<description>At least you didn&#039;t have my mySQL problem (that sounds strange!) I had a silly plugin that got spammed and then decided to query all the spams, 50k rows at a time! :(

You can guess how my host reacted!</description>
		<content:encoded><![CDATA[<p>At least you didn&#8217;t have my mySQL problem (that sounds strange!) I had a silly plugin that got spammed and then decided to query all the spams, 50k rows at a time! <img src='http://blog.terrypearson.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>You can guess how my host reacted!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
