Tuesday, 4 October 2016

Java on Windows - Why bitness matters

I kept seeing this: -


whilst trying to start Eclipse Juno which I'd downloaded as eclipse-jee-juno-SR2-win32-x86_64.zip

I'm using a 64-bit version of Windows Server 2008 R2

I did wonder whether the problem was related to the version of Java installed: -

java -version

java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) Client VM (build 25.101-b13, mixed mode)


java -fullversion

java full version "1.8.0_101-b13"

so I headed over here: -


and grabbed the 64-bit version of Java: -


Once installed, I checked the Java version again: -

java -version

java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)


java -fullversion

java full version "1.8.0_101-b13"

and retried Eclipse: -


Job done :-)

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...