[Remoterengine-devel] Launcher class checked in

[Ian Long]

Romain Francois wrote:
> On 09/28/2009 08:08 PM, Ian Long wrote:
>>
>> Hi,
>>
>> I have started work on and checked in a class that will launch the
>> REngineServer. The Launcher requires JAVA_HOME and R_HOME environment
>> variables to be set and uses these to build up the remainder of the
>> information required to launch the REngineServer - normally this is
>> performed by the "remoterengine" script within the exec directory.
>>
>> The goals of this script are to:
>>
>>     1. enable additional System properties to be set in the JVM running
>>        the server
>>     2. simplify the start up process
>>     3. make it easier to run the server in a debugger
>>     4. make it easier to run test harnesses around the server
>>
>> The script is mostly self-contained, the more interesting of the command
>> line options that it takes are:
>> -h Prints out a help message
>> -v Verbose mode
>> -t Test mode - doesn't try to run the server, builds the environment
>> list and writes it out to StdOut - also writes out a local file called
>> "launchcommand.txt" containing the command the Launcher would try to
>> execute in order to start the server.
>>
>> For example:
>>   >java -cp RemoteREngine-server.jar
>> org.rosuda.REngine.remote.common.Launcher -h
>> org.rosuda.REngine.remote.common.Launcher command line options:
>> Launcher -v -h -b path -c class -XMemoryDefinition<System Properties>
>>          -h: Print this menu
>>          -v: Verbose mode; default false
>>          -X: Java process memory defintion; default mx1024M
>>          -b: Path to root of class files (instead of
>> RemoteREngine-server.jar file
>>          -c: Class to be launched; default
>> org.rosuda.REngine.remote.server.REngineServer
>>          -D<propertyname>=<propertyvalue>: Set System property
>>          -t: Test mode - write out the launch command but do not 
>> execute it
>>
>> The Launcher works on Windows but currently is having issues on Linux.
>> The command written out to launchcommand.txt works, however the
>> interactive launch of the server does not - R generates a fatal error:
>> "Fatal error: you must specify '--save', '--no-save' or '--vanilla'"
>>
>> Cheers,
>> Ian.
>
> Thanks for this. I'll test on linux tomorrow. --save, --no-save or 
> --vanilla are typically one of the String you give to one of the 
> constructor of JRIEngine.
>
> Romain
>
The call within RemoteREngine_Server that fires up the JRIEngine has the 
args set to null, so unfortunately I still struggling to understand the 
reason for this.