-
Bug
-
Resolution: Not a Bug
-
Minor
-
8.0.1.GA
-
None
After the JBDS 8.1.0 GA installed with 32 bit JDK the JVM fails to start immediately (it returns with exit code 1). There is no log created. If the -vm argument removed from the ini, it don't falls back to default JVM. The configuration is listed above.
According alexeykazakov request, I created a new issue based on this comment JBDS-2513.
[JBDS-3512] JBDS wont start after installation (exit code = 1)
Denis Golovin (Inactive)
added a comment - Victor, thank you for update.
I glad to hear it is working now. My guess it was local configuration problem, because of this in devstudio.txt:
-vm c:\Program Files (x86)\Java\jdk1.7.0_79\bin\javaw.exe exit code = 1 C:\Program Files (x86)\Java\jdk1.7.0_79>java -version java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
I believe JBDS was installed as x86 and running as x86_64 in this case. Eclipse launcher could probably check at least java architecture is matches target install and show better error message instead just bizarre jvm error.
JBDS zip would not help here, but I'll follow up on this next release cycle and see if it can be improved on eclipse side.
Denis Golovin (Inactive)
added a comment - Victor, thank you for update.
I glad to hear it is working now. My guess it was local configuration problem, because of this in devstudio.txt:
-vm
c:\Program Files (x86)\Java\jdk1.7.0_79\bin\javaw.exe
exit code = 1
C:\Program Files (x86)\Java\jdk1.7.0_79>java -version
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
I believe JBDS was installed as x86 and running as x86_64 in this case. Eclipse launcher could probably check at least java architecture is matches target install and show better error message instead just bizarre jvm error.
JBDS zip would not help here, but I'll follow up on this next release cycle and see if it can be improved on eclipse side. 
Why does installation.png reference one jdk, but in jbdevstudio_err.JPG is different one?
I made a copy of JDK to prove not the whitespaces int the JVM path causing the problem, but both of them are the same jdk-s.
What is in devstudio.txt? Is it console output for all java installations you have?
Yes. I tried to run with all JDK-s but with 32 bit jre/jdk, I got exit code 1 and with 64 bit jdk/jre I got exit code 13. So 64 bit jdks are not interested in this case.
What is in your %PATH% env variable?
C:\Program Files\Dell\DW WLAN Card;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Skype\Phone
What would be output if you do something like this below?
This is also listed in jbdevstudio.txt
C:\>java -version java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
Now I made a copy of the JBDS, and after that I completely uninstalled, with the uninstaller.
I've run a new installation with the following settings, and the new installation works properly.
Installation path:
d:\jbdevstudio
Java VM path:
default
Components to install:
Red Hat JBoss Developer Studio 8.1.0.GA
Red Hat JBoss Enterprise Application Platform 6.3.0
Disk Space:
Available Disk Space: 53,82 GB
Required Disk Space: 825,78 MB
I've compared the two directories (old and new installation) and there were no major differences.
I zipped the not working copy (it is 650 MBytes), I can upload it somewhere if you think it may helps.
Viktor Csomor (Inactive)
added a comment - - edited Why does installation.png reference one jdk, but in jbdevstudio_err.JPG is different one?
I made a copy of JDK to prove not the whitespaces int the JVM path causing the problem, but both of them are the same jdk-s.
What is in devstudio.txt? Is it console output for all java installations you have?
Yes. I tried to run with all JDK-s but with 32 bit jre/jdk, I got exit code 1 and with 64 bit jdk/jre I got exit code 13. So 64 bit jdks are not interested in this case.
What is in your %PATH% env variable?
C:\Program Files\Dell\DW WLAN Card;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Skype\Phone
What would be output if you do something like this below?
This is also listed in jbdevstudio.txt
C:\>java -version
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
Now I made a copy of the JBDS, and after that I completely uninstalled, with the uninstaller.
I've run a new installation with the following settings, and the new installation works properly.
Installation path:
d:\jbdevstudio
Java VM path:
default
Components to install:
Red Hat JBoss Developer Studio 8.1.0.GA
Red Hat JBoss Enterprise Application Platform 6.3.0
Disk Space:
Available Disk Space: 53,82 GB
Required Disk Space: 825,78 MB
I've compared the two directories (old and new installation) and there were no major differences.
I zipped the not working copy (it is 650 MBytes), I can upload it somewhere if you think it may helps. I cannot replicate it ether.
Why does installation.png reference one jdk, but in jbdevstudio_err.JPG is different one?
What is in devstudio.txt? Is it console output for all java installations you have?
What is in your %PATH% env variable?
What would be output if you do something like this below?
cd C:\ java -version
Denis Golovin (Inactive)
added a comment - - edited I cannot replicate it ether.
Why does installation.png reference one jdk, but in jbdevstudio_err.JPG is different one?
What is in devstudio.txt? Is it console output for all java installations you have?
What is in your %PATH% env variable?
What would be output if you do something like this below?
cd C:\
java -version
Thank you for your reply!