Forum: JRuby JRE not found - Windows installation of jruby 1.7.2

Hi,

I did install JRuby 1.7.2 Windows Executable+JRE (x64) [1] on
Windows 2008 and it did not work out of the box.

After the
installation (JAVA_HOME had not been set by the installer) I got 'Cannot
find Java 1.5 or higher.', setting JAVA_HOME to the JRE installed
together with jruby I got 'Cannot locate Java installation, specified by
JAVA_HOME:'.

Interestingly it did work, when I set JAVA_HOME to the
directory above the JRE (The jruby dir). This doesn't seem to be quite
right to me, or?

There is no other Java version installed on that
system. Details and log see below.

Regards,
Manfred

>jruby -v
Cannot
find Java 1.5 or higher.

>set JAVA_HOME=C:jruby-1.7.2jre

>jruby
-v
Cannot locate Java installation, specified by JAVA_HOME:

>jruby
-Xtrace log.txt
Cannot find Java 1.5 or higher.

>set
JAVA_HOME=C:jruby-1.7.2

>jruby -v
jruby 1.7.2 (1.9.3p327) 2013-01-04
302c706 on Java HotSpot(TM) 64-Bit Server VM
1.7.0_07-b10 [Windows
Server 2008 R2-amd64]


-------------------------------------------------------------------------------
log.txt
(with
JAVA_HOME=C:jruby-1.7.2jre)
-------------------------------------------------------------------------------


Starting platform...
 Binary name is: jruby

initPlatformDir:
trying to find executable on PATH
File "c:jruby-1.7.2binjruby.dll"
exists
Module: c:jruby-1.7.2binjruby.dll
Platform dir:
c:jruby-1.7.2
Parsing arguments:
 -Xtrace
 log.txt
-Xjdkhome is not set,
checking for %JAVA_HOME%...
%JAVA_HOME% is set:
C:jruby-1.7.2jre
JvmLauncher::initialize()
 javaPathOrMinVersion:
C:jruby-1.7.2jre
checkJava('C:jruby-1.7.2jre', 'jre')
File
"C:jruby-1.7.2jrejrebinclientjvm.dll" does not exist
File
"C:jruby-1.7.2jrejrebinserverjvm.dll" does not exist
File
"C:jruby-1.7.2jrejrebinjava.exe" does not
exist
checkJava('C:jruby-1.7.2jre', '')
File
"C:jruby-1.7.2jrebinclientjvm.dll" does not exist
File
"C:jruby-1.7.2jrebinserverjvm.dll" exists
File
"C:jruby-1.7.2jrebinjava.exe" exists
File "C:jruby-1.7.2jrebinjavaw.exe"
exists
*** No need to clean the binary name:
jruby
constructBootClassPath()
File "c:jruby-1.7.2libjruby.jar"
exists
addToBootClassPath()
 path: c:jruby-1.7.2libjruby.jar

onlyIfExists: true
File "c:jruby-1.7.2libjruby.jar" exists
File
"c:jruby-1.7.2libjruby-complete.jar" does not exist
BootclassPath:
c:jruby-1.7.2libjruby.jar
constructClassPath()
addJarsToClassPathFrom()

dir: c:jruby-1.7.2
addToClassPath()
 path: c:jruby-1.7.2libjruby.jar

onlyIfExists: false
No need to add "c:jruby-1.7.2libjruby.jar" to
classpath, it's already in bootclasspath
No explicit classpath option is
used, looking up %CLASSPATH% env
ClassPath:
JvmLauncher::initialize()

javaPathOrMinVersion: 1.5
JvmLauncher::findJava()
 javaKey:
SoftwareJavaSoftJava Development Kit
 prefix: jre
 minJavaVersion:
1.5
getStringFromRegistry()
 keyName: SoftwareJavaSoftJava Development
Kit
 valueName: CurrentVersion
RegOpenKeyEx() failed. Cannot create a
file when that file already exists. (183)
JvmLauncher::findJava()

javaKey: SoftwareJavaSoftJava Runtime Environment
 prefix:

minJavaVersion: 1.5
getStringFromRegistry()
 keyName:
SoftwareJavaSoftJava Runtime Environment
 valueName:
CurrentVersion
RegOpenKeyEx() failed. Cannot create a file when that
file already exists. (183)
Cannot find Java 1.5 or higher.
Console is
attached.
onExit()



Links:

>>jruby -v
> Cannot
> find Java 1.5 or higher.
>
>>set JAVA_HOME=C:jruby-1.7.2jre

is it missing backslashes?
See also http://jira.codehaus.org/browse/JRUBY-6696

Am 19.02.2013 22:52, schrieb Roger Pack:

>>> jruby -v
>> Cannot
find Java 1.5 or higher.
>>
>>> set JAVA_HOME=C:jruby-1.7.2jre
>
> is
it missing backslashes?

No, must be a mail problem.

> See also
http://jira.codehaus.org/browse/JRUBY-6696 [1]

And also
https://jira.codehaus.org/browse/JRUBY-7104 [2]

Manfred


Links:

We had to release 1.7.3 for security reasons so I did not get this
particular launcher issue fixed (although I did fix another one).  We
will try and get this addressed soon and rolled into a jruby-launcher
gem release so you won't have to wait too long...I am fairly certain
your bug is JRUBY-7106 which involves a failing reigstry check.

-Tom

On Thu, Feb 21, 2013 at 8:13 AM, Manfred Usselmann
<usselmann.m@icg-online.de> wrote:
> No, must be a mail problem.
>
>
>
> See also http://jira.codehaus.org/browse/JRUBY-6696
>
> And also https://jira.codehaus.org/browse/JRUBY-7104
>
>
>
> Manfred



--
blog: http://blog.enebo.com       twitter: tom_enebo
mail: tom.enebo@gmail.com