You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Adam Mlodzinski <Ad...@quest.com> on 2011/01/13 18:49:11 UTC

[daemon] Procrun registry lookups

I have another question about 64-bit vs. 32-bit registry locations and procrun.exe.

Which location (plain, or Wow6432Node) is used for auto jvm lookups? The 64-bit Windows server I'm looking at right now has "Java Development Kit" and "Java Runtime Environment" under the 32-bit location, but it also has "Java Runtime Environment" under the plain (64-bit?) location.
I suppose the 32-bit builds would have to use the 32-bit dlls, hence the 32-bit registry location, while 64-bit procrun would have to use 64-bit jvm.dll, hence the 64-bit location. Is that correct?


--
Adam M.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


Re: [daemon] Procrun registry lookups

Posted by Mladen Turk <mt...@apache.org>.
On 01/13/2011 06:49 PM, Adam Mlodzinski wrote:
>
> I suppose the 32-bit builds would have to use the 32-bit dlls, hence the 32-bit registry location, while 64-bit procrun would have to use 64-bit jvm.dll, hence the 64-bit location. Is that correct?

Yes. No translation is done for detecting the JVM.

However currently, this might create problems at install time
if the 64 and 32 Java keys are out of sync (but I'm working on it)


Regards
-- 
^TM

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org