JDev 11g on Win7 x64

Question

Hi!
Yes, I know that JDev is not certified on Windows 7.
But I still would like to ask if anyone has noticed a similar issues with other Windows x64 editions (Vista, XP):
Occasionally, I'm getting IDE errors like:
Performing action Update Working Copy...[ from oracle.ide.navigator.ApplicationNavigatorWindow ]
Invoking command: [ from oracle.ide.navigator.ApplicationNavigatorWindow ]
Sep 22, 2009 9:02:58 AM oracle.jdeveloper.model.JavaClassNode getDecompiledClass
SEVERE: decompiling C:\Oracle\Middleware\jdeveloper\modules\oracle.jsf_1.2.9\javax.jsf_1.2.0.1.jar!\javax\faces\model\DataModel.class using "c:/progra~1/decomp/jad.exe -& -p -b -ff -nl -pi99999 -space -t2 -noinner"
java.io.IOException: *Cannot run program "c:/progra~1/decomp/jad.exe": CreateProcess error=2, The system cannot find the file specified*
     at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
     at java.lang.Runtime.exec(Runtime.java:593)
...Looks like JDev have problems with 8.3 path composition. On 32-bit Windows the c:/progra~1/ point to c:/program files/ where 32-bit JDK resides. But on x64 Windows versions, the 32-but programs are located in c:/program files (x86)/ and the 8.3 path is c:/progra~2/ (notice ~2 instead ~1). So, looks like JDev has soem paths hardcoded incorrectly for working on x64 platforms (with 32-bit JDK). If 64-bit JDK is used, it would work (as 64-bit apps are stored in c:/progra~1/ on 64-bit OS) but JDev don't like 64-bit JDK (didn't tried with latest update, though)...
This looks like bug to me.
Does anyone have a solution for this? I searched .conf files for this hardcoded path to change it, but didn't find (don't want to mess inside jars).
Regards,
Pavle

Answer 1

This comes from a previous thread - see Upgrading to JDeveloper 11.1.1.3 Tell us you're experience.
On a 4GB RAM Mac OS X, you could minimise (performance / hanging) problems with a config such as the following:
set AddVMOptions:
Xms1536M and Xmx1536M in .../jdeveloper/ide/bin/ide.conf
and
-XX:MaxPermSize=512M in .../jdeveloper/jdev/bin/jdev.conf
Customise VMOptions to suit your particular env.
This config handles the running of the Integrated WLS Server plus a deployment inside.
A precaution: Before exiting JDev - it's recommended to gracefully :-) terminate the Integrated WLS Server and the deployment - otherwise you may just break your JDev, with sometimes 'unstartable' consequences :-)
If you can't start JDev normally - for a reason, perhaps due to the Integrated WLS Server (weblogic.Server) and deployment still running in memory after a JDev accident :-),
then you may be forced to do a cmdline unix, ps -ef | grep java - identify the runaway WLS process_ids, then do a (sudo) kill -9 process_ids - don't do this at home :-)
- in some instances this could again lead to 'unstartable' consequences :-)
Then the other option is to fix JDev in the filesystem. Disabling some extension / plugins could also assist.
A first line-of-defence: backup a working version of your Jdev install dir with it's working extension / plugins.
/* JDevelopers of the world unite - Java processes don't run away parentlessly :-) */