JDBC Connection Issue
in [Java Help]
|
Prev: Hashcode and Equal
Next: Exception Handling
From: markspace on 11 Mar 2010 00:52 jross wrote: > > while [ 0=0 ];do nc -vvvz 127.0.0.1 3306;done > Glad you found something out. Can you just upgrade the Connect/J driver with out touching the Java version? Upgrading the Connect/J driver sounds like the easiest thing to do. Thanks for posting that nc command btw. There's so much crazy, useful stuff in Unix that I just don't know about most of it. I need a *nix cook book of useful commands or something.
From: jross on 11 Mar 2010 01:11 markspace wrote: > Glad you found something out. Can you just upgrade the Connect/J driver > with out touching the Java version? Upgrading the Connect/J driver > sounds like the easiest thing to do. Yeah I updated to MySQL 4.1, JDBC Driver 3 and JAVA 1.5 and all worked fine. Running JDBC 3 under java 1.4 and 1.3 complained about an exception Could not find the Class Savepoint, which must be new in 1.5, I could work around this, but I'm going to find another way of doing it like running the command "mysql -Bse "use db; select COUNT(*) from table;" and check if it returns a value It's good to know that perl wasn't the problem. > Thanks for posting that nc command btw. There's so much crazy, useful > stuff in Unix that I just don't know about most of it. I need a *nix > cook book of useful commands or something. > No worries I got plenty of them in my pocket =) Thanks for your time and effort Cheers Joel.C
From: Arne Vajhøj on 11 Mar 2010 21:56 On 10-03-2010 23:57, Lew wrote: > Lew wrote: >>> That said, I also was just on a project that still uses 1.4. To their >>> credit, they're finally now upgrading (gradually) to the (also now >>> obsolescent) Java 5. >>> >>> The actual conversion took about a week for roughly a million lines of >>> code. > > Arne Vajhøj wrote: >> But how long time did it take to retest? > > The test suites ran in a few hours. > > They had extensive test suites in place already. Didn't they do a full test? (unit tests is not a full test) Arne
From: Lew on 11 Mar 2010 23:19 Lew wrote: >>>> That said, I also was just on a project that still uses 1.4. To their >>>> credit, they're finally now upgrading (gradually) to the (also now >>>> obsolescent) Java 5. >>>> The actual conversion took about a week for roughly a million lines of >>>> code. Arne Vajhøj wrote: >>> But how long time did it take to retest? Lew wrote: >> The test suites ran in a few hours. >> >> They had extensive test suites in place already. Arne Vajhøj wrote: > Didn't they do a full test? Yes. I don't recall implying that they didn't. > (unit tests is not a full test) I did not say unit-test suites. They had extensive test suites in place already. Nor did they stop testing after just a few runs. Most of the code was not changed at all; only a few classes were affected by the conversion. As a matter of fact there is a regular and ongoing practice of testing at various scale on that project, including performance tests. While I have issues with a number of aspects of the coding and testing standards there, the tests were sufficient to reveal potential difficulties with the conversion to Java 5. In fact they did uncover the only issue that actually occurred, a reliance on references to the 'class' literal to initialize classes, and that was in the Apache commons-lang library, not the project-specific code. Since then, the system has gone into production with no further difficulties. The fact is that the conversion from Java 1.4 to 5 on that project was fast, about a week for about a million lines of Java code, uncovering only the issue in the third-party library. They got around that by using Java enums in place of the commons-lang version, and using a few hacks to communicate values between the Java 5 servers and those still running Java 1.4 and the commons-lang library. I'm really not sure where you're going with your questions and comments, Arne. I get the impression you're trying to make out that upgrading from Java 1.4 to Java 5 is harder than it really is. -- Lew
From: Kevin McMurtrie on 12 Mar 2010 23:35
In article <4b9723b9$0$5262$c3e8da3(a)news.astraweb.com>, jross <joelc(a)cognyx.com> wrote: > Current Java thread: > at java.net.InetAddressImpl.getLocalHostName(Native Method) You OS needs to be patched for a common multi-threading bug in the name resolver. -- I won't see Google Groups replies because I must filter them as spam |