64 bit jdk

Using the 32-bit build of Eclipse and a 32-bit VM works fine on 64-bit platforms. I’ve tried it on Windows 64-bit (Win 2k3) and Ubuntu 64-bit, both worked fine.

two questions about that…

#1) is there any chance this will be, uhh… “fixed” in the next release? After all, 64 bit is becoming more and more common, especially on Linux.
#2) speaking of which… I’m just in the process of switching to Linux or at least dual-boot. I’ve installed Java, Eclipse and MyEclipse on the latest Ubuntu 64-bit and so far, it seems to work! (I haven’t used it much yet, I’m still in the process of installting everything I need for “daily use”. “When” would the problem typically appear? I’ll have to check if I use 64 bit versions of everything, but since I’ve installed from the repositories, I’d definitely think so…

Thanks for any info…

@support-rkalla wrote:

… and besides the cool factor, no one currently needs to run MyEclipse with larger than 2GB heap so the reality of *needing* (not wanting, but needing) a 64-bit version is a very hard sell to management to derail other development efforts and new features just to address it.

ok, first of all: I know what you mean. There can be a (perceived *g*) “need” for the 64-bit version of Linux, but not really for the 64-bit version of Eclipse/MyEclipse.

HOWEVER… (to help you make the point to management):
– As a “stupid user”, I consider this a bug, not a (missing) feature. Everything else (from the Java world…) seems to work fine, so a crash is something that I just expect to be fixed…
– if I have to install a new version of Eclipse and my plugins, that’s extra work and I won’t be a happy customer. Also, I’d have to manually install Eclipse instead of using the version from the repositories which will also be additional work in the short and in the long run.
– I may be naive (or just optimistic? maybe because it currently works for me?), but I don’t think this would be a huge project that would take weeks… afaik, you’ll start posting 6.0 milestones “very soon” (or so I heard). It would be a good start to have a forum thread for 64-bit and treat those problems like any other (low to medium priority) bug. Maybe you can’t fix all of them (hey, it’s not like all the features work in 32 bit *eg* – err, sorry…), but maybe some of them are easily fixed?

@support-rkalla wrote:

1) Unfortunately it’s logistics. 1 of the developers has a 64-bit machine,

*lol* – you’re kidding? Having a 64-bit machine for testing takes 300 dollars and two hours for setting it up (not a very complete installation, but one that can be used for testing and some troubleshooting).

@support-rkalla wrote:

2) Hmm yes if you used Synaptic you are probably using 64-bit versions of stuff… I’m surprised it’s working… maybe something changed at some point and things got more stable?

Yeah, maybe. One of the first things I did was ditching the standard gcj 1.4.2 that came with Linux. I installed the latest Java 6 and I also use Java 6 to launch Eclipse and Tomcat. Maybe that helps? I don’t remember exactly why I did it, but iirc, there were some problems with that funny VM. No, I mean it’s really *great* that it was around when there was no official JVM, but why should I use it now with an official Java 5 and an official Java 6? It’s just so much faster!
Maybe that also makes the difference for stability?

Anyway – Java 6 on a 64-bit machine is fun 🙂
My Tomcat 5.5 with a small webapp starts up in 1800 ms in debug mode 🙂
(ok, may be as fast on 32 bit, but please don’t tell me 🙂

@support-rkalla wrote:

Some of the issues you will see are things with the Web 2.0 browser and AJAX debugging and the designer not working correctly.
But hey if it works, run with it 🙂

I will 🙂
Also, something “not working correctly” is a pity, but “the jvm terminating” is really bad.

If that helps you (or anybody), I’ll be happy to try some specific feature to see if my jvm also terminates… 😉

I’m running Java 6, Eclipse 3.2.2 and MyEclipse 5.5.1. Currently I’m in the trial version but everyting has been working great, except for one thing. I can’t get MyEclipse to take take my subscription code I paid for to that at the end of the trial it doesn’t stop working. Quite frankly I’m going to ditch MyEclipse before I ditch the other stuff and downgrade to 32 bit everything.

Ok, I just got an email from MyEclipse and here is what worked for the problem I described having earlier

1) Shut down MyEclipse
2) Go to your home dir ($HOME)
3) Create a new file named “.myeclipse.properties” without quotes obviously.
4) Enter this as the contents of the file (everything between the lines)
————————–
#MyEclipse global properties
#Wed Jan 24 12:01:57 MST 2007
LICENSE_KEY=” the key you purchased”
LICENSEE=”your user anme”
————————–