I'd like to bump up this feature request. Any status on this?

Michael

Michael,

Beyond just supporting the 64 bit version of Eclipse, we do have some other technical issues with a few features that could cause problems running in that version of Eclipse, which is why it's not just a slam dunk deal.

Support for this is not planned in 8.5, but I will look into this and see what I can do, I realize it would be good to have a "true" 64 bit version. I will update this thread as more details become available. Sorry for the inconvenience.

Brian,

I understand there are some technical hurdles. A true 64-bit version would be great. I won't be using MyEclipse until that happens, as I don't want to have two versions of Eclipse on my system, and Netbeans does just fine for now. Thanks for the update.

MIchael

Hm, It's not quite clear to me what or how a 64 bit version of MyEclipse would benefit me. I've been using x64 versions of Windows Vista and 7 for over 2 years now, because of the opportunity to run several virtual machine side by side with VMWare, but I can't imagine advantages for ME. Could someone please give some explanations or reasons for this requirement a.k.a. demand?

TIA

huisma13 wrote:

Hm, It's not quite clear to me what or how a 64 bit version of MyEclipse would benefit me. I've been using x64 versions of Windows Vista and 7 for over 2 years now, because of the opportunity to run several virtual machine side by side with VMWare, but I can't imagine advantages for ME. Could someone please give some explanations or reasons for this requirement a.k.a. demand? TIA

The major benefit of using 64bit application is the memory addressing. But it is not for everyone.

I am personally haven't use the 64bit of eclipse since myeclipse doesn't support it under windows so far.
However, I am working on a project that has Tens of Thousands java classes. For which, even in the ant build script, I have to increase the max memory heap size to 1GB to compile them, otherwise, the compilation will run OOM. I can imagine that if the whole source files were added to eclipse with myeclipse plugin, it will eventually run out of memory too. Since the 32bit of OS only support 4GB memory (max, for most cases it is less since hardware will use some of the resource too). And this is the not the max memory any application can use, the truth is for single process under 32bit windows, the total amount of memory that can be addressed is less than 2GB.

For some people who is developing a huge project in myeclipse could eventually hit the memory limitation and the only possible solutions are 1, split the project into multiple smaller ones or 2, switch to 64bit IDE.

We are one of those cases (big projects causing issues with MyEclipse in a 32-bit JVM). Our project is so large that we actually push a 32-bit JVM to its limit. We have 75 projects, 23,000 files (10,000 Java source files, 7,200 JSPs). With bin and .svn folders, quadrouple this number to over 100k files.

We allocate 1024m of heap, and that's barely enough (not enough for everything in fact, the FindBugs validator will run it out of heap if we do a full validation). However, we can't go much larger than that because then we start running out of native memory or some other non-heap memory resource. When you increase the heap size, you're squeezing everything else out. MyEclipse (at least with our projects in it) is very unstable beyond 1024m heap (i.e. when a native call to allocate memory fails, MyEclipse dies pretty spectacularly). The 1024 is a balance between not running out of heap and not running out of some other non-heap memory resouse. A smaller heap and it runs out of heap. A larger heap and the frequency of the crashes from running out of some other non-heap memory resource go up dramatically.

We absolutely need the 64-bit version of MyEclipse 8 (i.e. MyEclipse running on Eclipse for 64-bit running on a 64-bit JVM). We were so looking forward to this. The last I checked this thread the response was "we'll support 64-bit JVMs in the first patch right after the 8.0 release", to now "not even planned for 8.5". That's very dissapointing. The productivity loss we have to endure from only being able to do a 1024m heap (lots of GC wait and freezes during heavy GC/load), as well as the instability from the IDE crashing all the time (either out of heap, or out of some other non-heap memory resource) is a real drag. It is a substantial loss of productivity for our whole organization.

Here's +70 votes for the 64-bit JVM and large heap support for MyEclipse in the near future.

Can't agree more. 64-bit is a must have for us.

Maybe you could give the community some idea of what these hurdles are and see how we can help? Long shot perhaps, but maybe the features are not even important enough to justify holding back a 64-bit release where those are just not available?

hi,
I agree with you guys that 64bits is gonna be important in coming development.
Just hope it is available after 8.5 release.

I wholeheartedly agree that true 64-bit support is needed with ME. We have also hit the wall with a very large product that is already broken up into nine different modules. We are having trouble running some parts of the builds in eclipse without using the maximum amount of memory possible. Every time we add something to the product, it is iffy if the build will fail. We end up fiddling with the heap space settings and unloading everything we can.

I switched to the 64-bit version of eclipse (3.5.2) under Win7 and it works beautifully. No memory problems, and I don't have to break up two more modules (a real pain).

Hey,

It's me again. Anyone have any forecast about when should be available one 64bits version for Windows??? I'm using Windows 7 Pro 64bits, most of time it works well, though when is needed work with several threads and more memory, usually the system crash, apart that should be better and faster than 32bits.
One other thing, is there any way to create the binding classes, for JAXB, from inside IDE? Because now I'm using the XJC.EXE file into command window. If does not exist, do you have any forecast to implement it? When I need create it for several schemas there are two options, type for each one that take a lot time or start use the Netbeans, that provide this feature and it's quite good for signal.
Thank you

support-nipun wrote:

A 64-bit version for WIndows is absolutely planned, we will likely release it soon after our 8.0 GA release goes out or with 8.1 -- we haven't ironed out the final QA for that release yet, but it's definitely coming

This was posted in October of 2009. It's now June 2010, and there is still no release of MyEclipse 64-bit for Windows. Any update on this?

We just tried using the 64-bit version of Eclipse 3.5.2 with the 8.5 udpate site, and no luck. It didn't work. We got pretty much the same error message mpassell did when he tried with the 8.0 version of the update site (same error message, except instead of being MyEclipse Enterprise Workbench 8.0.0 it was MyEclipse Enterprise Workbench 8.5.0).

So, when can we expect a 64-bit version of MyEclipse for Windows? It's been nine months since this original promise of "soon after our 8.0 GA release" and we're seriously considering leaving MyEclipse and figuring out how to make our set of projects work with straight 64-bit Eclipse. We do not want to invest that time if we do not have to though, so, can we get an ETA please?

JC,

We have been looking at the Windows 64 bit issue. Unfortunately our initial attempts have not succeeded (as far back as 8.5M2), but we are still working on it. It will be reprioritized after the 8.6 release, believe me - we realize the pressing need for this as several of us are on 64bit environments ourselves.

The problem we are facing with 64bit support is primarily finding a compatible 64bit build of XULRunner. Without XULRunner, the html / jsp design panes, REST explorer and AJAX debugger would stop functioning. I'm not saying we would create a release like this - but would a 64 bit product with these features be missing suit your specific needs? I'm guessing not, but I had to ask.

Any update on that?
Now it's July 2010 and MyEclipse 8.6 out.
Still I can't find info about 64 Bit Windows 7 Support?!?!?

Mobilexag,

Please see my previous comment. We realize the importance of the problem and are prioritizing this for the 9 release. No work on this has been done in the 8.6 timeframe as something like this just does not fit into the timeline of a minor release.

Support-Brian wrote:

The problem we are facing with 64bit support is primarily finding a compatible 64bit build of XULRunner. Without XULRunner, the html / jsp design panes, REST explorer and AJAX debugger would stop functioning. I'm not saying we would create a release like this - but would a 64 bit product with these features be missing suit your specific needs? I'm guessing not, but I had to ask.

Yeah, that would work fine for us. We don't use design view, it's too slow, and WYSIWYG development of JSPs is for beginners. We're all pretty good with JSP and HTML, and modifying the JSP and refresing the browser window to see the REAL results (with data) is so much better than anything the design view can present. As well, the Visual JSP debugger crashes the JVM from time to time (in the XUL code, coincidentally), and hangs with certain JSPs with applets embedded, so we've all switched over to using the non-visual JSP editor anway. As well, most of our new development is in Flex. We installed Flex Builder 3 plugin into MyEclipse. So we really don't even do that much new HTML/JSP development anymore, but we still have over 2500 JSPs to maintain.

We don't use the REST explorer or AJAX debugger.

As long as the Maven4MyEclipse works (so we can build), we can edit files, hot code swap Java, auto-complete, syntax highlight, deploy to Tomcat 6, debug Java and JSP, and get Tomcat stdout and stderr to the console, we're all set.

Helios (Eclipse 6.4) is out, including 64-bit versions of all platforms (classic, JEE, etc). There should be a 64-bit XULRunner in there, right? We've actually gotten our app almost up and running in Helios 64-bit. We don't like the fact that the maven + deployment doesn't work (so we have to use in situ deployment configurations, which isn't very close to production, and a bit harder to view what the final result will look like during development, we really like the deployment which builds the actual WAR structure as a copy of everything in Eclipse into Tomcat). Otherwise, everything else seems to be working. We'll have to use it for awhile to be sure and see what else we might be missing. Our build times dropped by about 25% with 64-bit and 2GB of heap, and hopefully our stability will go up now that we won't hitting other non-heap memory limits on we were hitting with the 32-bit address space.

So, can you leverage anything in Helios to get a MyEclipse 64-bit for Windows working soon? Can you release one with the features backed by XULRunner disabled?

In any event, we're about to make the switch and start using Helios JEE 64-bit. If we don't get a solution from Genuitec soon (like in the next couple of weeks), we will probably be converted over fully to Helios and may not switch back unless there is some compelling reason to do so.

So, where do we go from here?