StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><em>You haven't pasted all of your code in your question, so before trying the (complicated) way below, please rule out the simple causes and make sure that your fields <code>modelFile</code> and <code>rsession</code> are not declared static :-)</em></p> <p>If they are not:</p> <p>It seems that the way R sessions are created is OS dependent.</p> <p>On Unix it relies on the multi-session ability of R itself, on Windows it starts with Port 6311 and checks if it is still free. If it's not, then the port is incremented and it checks again, if it's free and so on.</p> <p>Maybe something goes wrong with checking free ports (which OS are you working on?).</p> <p>You could try to configure the ports manually and explicitly start different local R servers like this:</p> <pre><code>Logger simpleLogger = new Logger() { public void println(String string, Level level) { if (level == Level.WARNING) { p.print("! "); } else if (level == Level.ERROR) { p.print("!! "); } p.println(string); } public void close() { p.close(); } }; RserverConf serverConf = new RserverConf(null, staticPortCounter++, null, null, null); Rdaemon server = new Rdaemon(serverConf, this); server.start(null); rsession = Rsession.newInstanceTry(serverConf); </code></pre> <p>If that does not work, please show more code of your <code>Revaluator</code> class and give details about which OS you are running on. Also, there should be several log outputs (at least if the log level is configured accordingly). Please paste the logged messages as well.</p> <p>Maybe it could also help to get the source code of <em>rsession</em> from <a href="https://code.google.com/p/rsession/" rel="nofollow">Google Code</a> and use a debugger to set a breakpoint in <code>Rsession.begin()</code>. Maybe this can help figuring out what goes wrong. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload