9 messages in com.mysql.lists.javaRe: More Information Re: JDBC/mySQL i...| From | Sent On | Attachments |
|---|---|---|
| Pam Vermeer | 20 Sep 2002 11:00 | |
| Mark Matthews | 20 Sep 2002 11:43 | |
| Pam Vermeer | 23 Sep 2002 05:22 | |
| Solveig Albrand | 23 Sep 2002 05:41 | |
| Pam Vermeer | 23 Sep 2002 05:44 | |
| Pam Vermeer | 23 Sep 2002 06:10 | |
| Mark Matthews | 23 Sep 2002 06:46 | |
| Solveig Albrand | 23 Sep 2002 06:54 | |
| Mark Matthews | 23 Sep 2002 08:00 |
| Subject: | Re: More Information Re: JDBC/mySQL inconsistent getting connection |
|---|---|
| From: | Mark Matthews (ma...@thematthews.org) |
| Date: | 09/23/2002 08:00:54 AM |
| List: | com.mysql.lists.java |
----- Original Message ----- From: "Solveig Albrand" <albr...@isn.in2p3.fr> To: "Pam Vermeer" <verm...@earthlink.net>; <ja...@lists.mysql.com> Sent: Monday, September 23, 2002 8:54 AM Subject: Re: More Information Re: JDBC/mySQL inconsistent getting connection
Pam, Yes that's the same error as I get, after 13 minutes or so. You just said in a later mail that the timing is different in your case. That may not be significant though, I have no idea what determines the13 minute timing I observe. Timing to connect and do queries etc. depends on the network routing, (i.e. Japan - France is MUCH longer than Switzerland-France) so perhaps this error does too.
Well I'm afraid that all this does not advance you very far - because I have no idea what to do about it, except hard work. (I do find it comforting though to feel less alone with this error.......)
If no timout is implemented in the driver, I was thinking of trying to patch the driver myself, I did some socket programming in a former life. Or, I could run my connect in a thread and put my own local timeout, since I can't get the driver timeout to work. I would prefer getting the driver timout to work though.
Perhaps Mark Matthews could give us his advice on the best course of
action?
Hopefully you saw the e-mail that went to the list earlier today. MySQL Connector/J 3.0.1 will allow you to give a socket timeout value. I'm looking at releasing it this week.
If you're experiencing router problems, you really should think about notifying your network people, because your network is broken, and there's nothing a JDBC driver can do about that.
Also, you might consider re-working the architecture of your application to be web-based, as there's a lot less communications involved over the network, and most network people can get websites to work. Once you throw other protocols into the mix, things can get goofy.
-Mark