Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / September 2009

Tip: Looking for answers? Try searching our database.

JDK 1.5.0_21 released

Thread view: 
Roedy Green - 08 Sep 2009 22:14 GMT
Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
just released.
Signature

Roedy Green Canadian Mind Products
http://mindprod.com

"I mean, source code in files; how quaint, how seventies!"
~ Kent Beck (born: 1961 age: 48), evangelist for extreme programming.

Lew - 09 Sep 2009 04:01 GMT
> Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
> just released.

But it is still officially supported.

Signature

Lew

Roedy Green - 09 Sep 2009 04:08 GMT
On Tue, 08 Sep 2009 14:14:59 -0700, Roedy Green
<see_website@mindprod.com.invalid> wrote, quoted or indirectly quoted
someone who said :

>Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
>just released.

Oops.
JDK version 1.4 reached its end of life on 2008-10-30, and Sun will no
longer support it. JDK version 1.5 is slated for end of life
2009-10-30. End of life does not mean all copies of JDK version 1.5
will suddenly turn into pumpkins. Apple will still offer its JVM to
download. Sun will still offer it in the archives. It is just that Sun
will no longer fix any bugs in it. To get the bug fixes, you must go
to version 1.6.

Signature

Roedy Green Canadian Mind Products
http://mindprod.com

"I mean, source code in files; how quaint, how seventies!"
~ Kent Beck (born: 1961 age: 48), evangelist for extreme programming.

Kevin McMurtrie - 12 Sep 2009 13:15 GMT
> Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
> just released.

Enterprise customers (as in buying Sun support) will demand 1.5
maintenance for a while.  1.6 requires source code changes, retuning,
and rediscovery of what bugs will be showing up.  Where I work, it
wasn't until last year that public builds of 1.5 were free of
catastrophic bugs with no workarounds.  A 1.6 update will have to wait
until business is slow.

Signature

I will not see your reply if you use Google.

Lew - 12 Sep 2009 17:17 GMT
>> Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
>> just released.
>
> Enterprise customers (as in buying Sun support) will demand 1.5
> maintenance for a while.  1.6 requires source code changes, retuning,

What code changes?

> and rediscovery of what bugs will be showing up.  Where I work, it
> wasn't until last year that public builds of 1.5 were free of
> catastrophic bugs with no workarounds.  A 1.6 update will have to wait
> until business is slow.

Google "technical debt".  Hopefully your business is too successful ever to be
slow.

Signature

Lew

Kevin McMurtrie - 12 Sep 2009 21:00 GMT
> >> Even though it is no longer officially supported, JDK/JRE 1.5.0_21 was
> >> just released.
[quoted text clipped - 3 lines]
>
> What code changes?

Primarily, JDBC delegates are not compatible.  1.6 defines new JDBC
methods with return types that don't exist in Java 1.5.  Proxies still
work but they're not always appropriate.

> > and rediscovery of what bugs will be showing up.  Where I work, it
> > wasn't until last year that public builds of 1.5 were free of
[quoted text clipped - 4 lines]
> be
> slow.

When I say that JVMs have "catastrophic bugs", I really mean
catastrophic.  We needed custom builds of 1.5 to avoid a file descriptor
bug that routed data streams completely randomly if Solaris NFS was in
use.  Files, JDBC connections, HTTP connections - all mixing together.  
And then there have been numerous GC bugs where a collector stops the
JVM for 2 minutes... 5 minutes... 10000 minutes.  Even today, Java 1.5
needs lots of -XX options to fix CMS self-tuning bugs.

There is no technical debt when no Java 1.6 features are needed yet.  
The update will happen when it's safe for business.

Signature

I will not see your reply if you use Google.

Mike Amling - 14 Sep 2009 03:44 GMT
> When I say that JVMs have "catastrophic bugs", I really mean
> catastrophic.  We needed custom builds of 1.5 to avoid a file descriptor
[quoted text clipped - 3 lines]
> JVM for 2 minutes... 5 minutes... 10000 minutes.  Even today, Java 1.5
> needs lots of -XX options to fix CMS self-tuning bugs.

  Yep. While we don't measure these things ourselves, our releases have
to be able to run on 1.4 because of customer sentiment that 1.4.2 was
the last "stable" release. We only ship code that uses post-1.4 Java
features if it's done via reflection.

--Mike Amling


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.