Timeline for Error loading module MySQL server has gone away
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2014 at 4:56 | vote | accept | Jobin | ||
| May 29, 2014 at 4:56 | comment | added | Jobin | @Anibal , Finally issue get fixed, Server Admin able to increase the mysql query execution time and issue get solved. | |
| May 22, 2014 at 13:06 | comment | added | Anibal | Even if you have intensive queries, MySQL process does not die and go away, you just get a timeout. | |
| May 21, 2014 at 21:57 | comment | added | Craig | VirtueMart has also been very MySQL intensive in the past, the latest are still pretty heavy in the complexity of their queries. | |
| May 21, 2014 at 19:01 | comment | added | Anibal | Yes, mysql issues seem to be arbitrary. As we can't check the source code, we can't verify which is the real trigger. E.g. internal index structures. That's why a simple version update solves the issue in a magical way :-O | |
| May 21, 2014 at 12:14 | comment | added | Jobin | Thanks for your answer. There is a strange thing on the same server another site with same joomla installation works fine. So if it is a Mysql issue it should be there too. But I am sure its not due to code bcoz both are working with same code. According to this situation I think both site have different DB size so Issue occurred site DB data is huge so the limit exceed. | |
| May 21, 2014 at 11:54 | history | answered | Anibal | CC BY-SA 3.0 |