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

Just released, a free O’Reilly book on Reactive Microsystems: The Evolution of Microservices at Scale. Brought to you in partnership with Lightbend.

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.

Strategies and techniques for building scalable and resilient microservices to refactor a monolithic application step-by-step, a free O'Reilly book. Brought to you in partnership with Lightbend.

Topics:

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}