Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Latest Java Update Fixes Eclipse Crash Issue

DZone's Guide to

Latest Java Update Fixes Eclipse Crash Issue

· Java Zone
Free Resource

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

A lot of Eclipse users had issues with the previous update of the JDK. Java 6 Update 21, caused issues with the memory settings after Oracle changed the vendor name in the executables for java and javaw. The bug describes the issue:
"This causes a severe regression for programs that need to identify the Sun/Oracle HostSpot VM such that they know whether the "-XX:MaxPermSize" argument needs to be used or not."


Basically, the eclipse.exe launcher checks if the 'Sun Microsystems' string is present in order to add the -XX:MaxPermSize VM parameter. On Monday, Oracle provided a new version (build 07) of Java 6 Update 21, reverting the vendor name back to Sun Microsystems Inc for the moment. So, if you haven't used the auto-update yet, you'll have nothing to worry about thanks to Oracle's fast reaction. 

Oracle will be changing the vendor name in Java 7, and there's already a patch available to deal with this change when it comes about.

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}