2.2250738585072012e-308It's the floating point number of death.
It was revealed several months ago that when creating this number in binary form, Java crashes or, as Oracle describes it, experiences "a complete denial of service." Both client and server versions are affected.
It's a weird bug but Oracle has fixed it now.
They have issued a standalone patch entitled Java SE Floating Point Updater Tool, but it's a JAR file that you have to run it manually and I had trouble getting it to work. It said it couldn't write to the temp directory. I can't imagine why not.
Oracle also announced that JRE 6 update 24 will include this fix and also be distributed with the Java SE and Java for Business Critical Patch Update - February 2011, scheduled for February 15.
What's even weirder about this bug is that it's was also in PHP and has been fixed there as well. Read the link, as it attempts to explain why this particular number is significant.
It was revealed several months ago that when creating this number in binary form, Java crashes or, as Oracle describes it, experiences "a complete denial of service." Both client and server versions are affected.
It's a weird bug but Oracle has fixed it now.
They have issued a standalone patch entitled Java SE Floating Point Updater Tool, but it's a JAR file that you have to run it manually and I had trouble getting it to work. It said it couldn't write to the temp directory. I can't imagine why not.
Oracle also announced that JRE 6 update 24 will include this fix and also be distributed with the Java SE and Java for Business Critical Patch Update - February 2011, scheduled for February 15.
What's even weirder about this bug is that it's was also in PHP and has been fixed there as well. Read the link, as it attempts to explain why this particular number is significant.
No comments:
Post a Comment