Mail Archive Home | enhydra List | May 2004 Index
| <-- Date Index --> | <-- Thread Index --> |
Hi, as we saw on the internet, this is known problem of MySQL database. We can't get that error, but on some forums (http://www.javalobby.org/thread.jspa?messageID=91797319&threadID=12478&forumID=159) we saw that solution is to set autoReconnect flag on MySQL connection. Can somebody try this and post results to list, maybe this is solution for this problem ? We will keep trying to get this error, and try to find out solution! Zoran Thursday, May 20, 2004, 10:02:49 AM, you wrote: PS> V Čt, 20. 05. 2004 v 03:28, Ryuji Hattori píše: >> Sometimes I find the same type exception using Enhydra 5.1-7 PS> we've been suffering this in Enhydra 5.1-7 as well so I tried to upgrade PS> to latest (since I saw some DODS fixes) but it didn't help. >> But in my case, an exception arize at connection allocation. PS> I believe we have the same problem. The symptoms are that sometime when PS> new user tries to enter the web site they get the exception. But if they PS> reload immediately the web app runs just fine. So it seems like PS> connection allocation problem. PS> I were also thinking if this could be caused by the MySQL closing unused PS> connections after 8 hours (that's what I heard somewhere) but the PS> "autoReconnect" and/or "autoReconnectForPools" should solve this issue. >> 2004-04-26 10:57:45,816: [Thread-3], ERROR, Wavebaby: RID:17510: Unhandled >> Application error in Wavebaby >> java.sql.SQLException: Communication link failure: java.io.EOFException, >> underlying cause: null PS> Yes, that's exactly the same case. PS> What can we do in order to fix it? This is a serious problem and since PS> it's so random it's hard to catch and debug it. PS> Petr
| <-- Date Index --> | <-- Thread Index --> |
Powered by MHonArc.
Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.