Wednesday, November 23, 2011

Eclipse: Failed to load the JNI shared library ... vm.dll

I managed to install OSB with OEPE 11.1.16 ( on win7 64-bit. My default JDK is 64-bit. When I fire up Eclipse, I'm getting this "Failed to load the JNI shared library ... vm.dll" error.

Solution is to install JDK 32-bit, then update eclipse.ini to point to your 32-bit JDK. here is the snippet of the .ini file. Keep in mind "-vm option needs to split on 2 lines, and appears before vmargs" (see

OSB install error: Specified oepe location is not a valid location

I'm re-installing SOA suite

The OSB I have is (

While installing OSB I encountered this "specified oepe location is not a valid location". However, the location I point to is the matching version OEPE (oepe-galileo-all-in-one-

After struggling for a long time, I downloaded, that did the trick.

I am not sure you see the irony, the matching verion OEPE doesn't work with OSB. I had to use a higher version OEPE oh, well :-(

Jdeveloper extension update

I always ran into issues when updating jdeveloper extensions after a fresh install. The standard steps are: Jdeveloper -> help ->  check for udpates, then select the extensions you need.

Although I don't have proxy, but a popup always asks me to use this proxy "", I uncheck proxy, the update ended up doing nothing.

It didn't help, their "official" extension center ( doesn't even have the SOA composite editor :(

Well, for today, this is how it is "working" for me: like I said, I do not use proxy from my network to internet, but after numerous failed attempts, i finally logged onto a VPN. It beats me that within the VPN, the update actually worked! Go figure! I'm logging it here, in case, I have to go through the same thing in 6 month again...