Re: [Rd] problem using rJava with parallel::mclapply

2014-06-19 Thread Jeroen Ooms
On Mon, Nov 11, 2013 at 6:20 PM, Simon Urbanek wrote: > > It’s a limitation of the Java runtime - you cannot fork a JVM. This is true > for most libraries that use long-lived threads or any kind if UI (see the > warnings in mcfork). Is there some way to reset or restart the JVM within the fork?

Re: [Rd] problem using rJava with parallel::mclapply

2013-11-11 Thread Simon Urbanek
On Nov 11, 2013, at 12:40 PM, Karl Forner wrote: > Dear all, > > I got an issue trying to parse excel files in parallel using XLConnect, the > process hangs forever. > Martin Studer, the maintainer of XLConnect kindly investigated the issue, > identified rJava as a possible cause of the problem

Re: [Rd] problem using rJava with parallel::mclapply

2013-11-11 Thread Karl Forner
Thanks Malcolm, But it does seem to solve the problem. On Mon, Nov 11, 2013 at 6:48 PM, Cook, Malcolm wrote: > Karl, > > I have the following notes to self that may be pertinent: > > options(java.parameters= > ## Must preceed `library(XLConnect)` in order to prevent "Java >

Re: [Rd] problem using rJava with parallel::mclapply

2013-11-11 Thread Cook, Malcolm
Karl, I have the following notes to self that may be pertinent: options(java.parameters= ## Must preceed `library(XLConnect)` in order to prevent "Java ## requested System.exit(130), closing R." which happens when ## rJava quits R upon trapping INT (control-c), as is do