A serious bug between Java and Debian

After a recent upgrade of my Debian testing (squeeze) I was hit by a Sun Java bug that was so serious that the only thing I could say was "wow".

There is a bug in Sun JVM that is revealed by a new default networking setting in Debian. What is the effect of this bug? Nothing less than the total breakage of Java networking. I can't stress how serious it is (if you still don't realize it, think about Java debugging, servlet containers, JMX etc.), but according to the comments on both bugs neither of those organisations is interested in fixing it! This is really scary.

As a side note I would like to point out that I lost another hour or two of my life because of this bug, since the symptoms are not giving you a smallest clue. In my case I saw this after starting Tomcat from Eclipse in debug mode:

FATAL ERROR in native method: JDWP No transports initialized

And some other useless crap. I'm becoming too old for this, I have better things to do in my life...

Last update
201006300000