When I started this job at unamed company, it was my return the Java development world after a hiatus of about seven years.
In my day, we used xemacs, xterms, and Netscape Communicator and we liked it!But seriously, when I last seriously wrote Java, there were some not-so-useful proto-IDEs out there. My short return in 2002 didn’t show that the world was much better.
But in 2006, Eclipse is king. And since I spent most of time in Eclipse, cranking out the objects, I didn’t mind too terribly to be working on Windows. But those who know me know that I prefer to use Linux and my 10-year old FVWM config (ported a few years back to fvwm2) to get “real work” done.
So after 6 months on Windows, I switched to Linux (Fedora Core 5, for the curious… I’m a total Red Hat whore). Eclipse is pretty much the same. The only problem was that the debugger seemed to run painfully slow. I’ve lived with this for like 3 months. And finally, FINALLY, I have a remedy:
Small JDWP packets with the socket transport causes slow debugging on linux 2.6.15 kernel and newer
I installed jdk-1.5.0_08 and suddenly the sun is shining, the birds are singing, and the debugger is responsive again!
What was the problem? Evidently, the debugger was behaving badly, but this was masked by some behavior in the Linux kernel that was fixed in version 2.6.15:
Java remote debugging is slow due to apparent networking bug
Hallelujah!