February 01, 2011
Mark Wielaard: New GPG key.
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f...
More »
February 01, 2011
Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!.
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
The IcedTea project provides a harness to build the source code from OpenJDK6 u...
More »
November/2024
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| | | | | | 1 | 2 | | 3 | 4 | 5 | 6 | 7 | 8 | 9 | | 10 | 11 | 12 | 13 | 14 | 15 | 16 | | 17 | 18 |
19 | 20 | 21 | 22 | 23 | | 24 | 25 | 26 | 27 | 28 | 29 | 30 | | | | | | | | |
|
 |
Have you upgraded your Java 1.6_21 to Java 1.6_21?
I download the newest release of Java when it comes out.
As precaution, I run with the newest versions for a while prior to recommending my clients to upgrade.
The first week with 1.6_21 was hell. Tomcat was running out memory, both NetBeans and Eclipse routinely died.
I patched my environments by setting with -XX:MaxPermSize set to 512m.
I found out the cause of my problems: http://tinyurl.com/38nr6v8 A bug arose when Oracle changed the company field name in Java from "Sun Microsystems, Inc" to "Oracle Corporation".
I went to Java.com to see if I was running the latest/greatest. The nice little display said I was running the latest.
I used Java –version to verify, which returned Java 1.6_21-b06.
Reading the articles and blogs, 1.6_21-b06 was incorrect. The latest was 1.6_21-b07.
I went the JDK route, which uninstalled, and then installed the latest. Now my environment says Java 1.6_21-b07.
It would be nice if Oracle would have Java.com actually look at subversions, or had this patch actually Java 1.6_22. Yes, it’s embarrassing, I’m embarrassed for Oracle, but don’t let Java 1.6_21-b06 hanging out there by simply not updating the Java.com site.
Date: August, 09 2010
Url: http://www.java.net/blog/malcolmdavis/archive/2010/08/09/have-you-upgraded-your-java-1621-java-1621
Others News
|
