commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Hagedorn <>
Subject Re: [daemon] Unable to find Java Runtime Environment
Date Tue, 14 Sep 2010 08:29:18 GMT
 --StartMode=java --JavaHome=jre ends up in
[error] ServiceStart returned 5
I guess '5' means access denied. So it needs a valid --JavaHome
(--StartMode=jre wont work too).

BTW my very favorite StartMode would be 'jvm' of course but it fails.
I'm using RMI within localhost (talking from the daemon app to gui). If
daemon app gets launched by jvm.dll I catch exceptions cause of missing
security manager for RMI class loading. But I don't want to use security
manager and if my app gets launched by java.exe is do not need one.
Is this dependency forced by prunsrv or is this a built in feature of
jvm.dll? And what does java.exe to skip security manager in case of
local usage? Is jvm.dll assuming web browser usage by default?


On 13.09.2010 18:26, Mladen Turk wrote:
> On 09/13/2010 05:43 PM, Michael Hagedorn wrote:
>>   Thanks for the quick answer!
>> To pick up the java.exe by registry would be great too. I don't want to
>> care about JAVA_HOME. If user upgrades JRE service should still work. In
>> case of jvm.dll it will. Why not with java.exe?
> Indeed, why not.
> Although -Jvm=xxx is meant for --StartMode=jvm.
> Perhaps --JavaHome=jre would do the trick.
> Currently for StartMode=java and without --JavaHome
> procrun will search for JDK (not JRE) from the registry.
> We could fallback to searching for JRE if JDK was not found.
> Anyhow, create a JIRA feature request for Commons Daemon.
> Regards

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message