Hi --
Just fyi about location server stuff. To see if it is running, grep for java processes on graphics or city. Look for a java proc with tons of command line args (i.e. java -rmi ......). The other thing to look for is rmiregistry, which needs to run in the background for rmi to work. In general, this is always running on graphics/city. Note that the loc server chews up around 500 MB of memory.
-Patrick
Hi all,
two quick things.
1. There should only be *one* java rmi proc running on the server with the loc server
2. can someone move my BMG list membership from pnichols@mit.edu to pnichols@graphics.lcs.mit.edu?
Thanks, Patrick Thx.
Ok, so:
1. kill all the rmi procs 2. run rmiregistry& 3. checkout the loc server. cd walkthru/mit/src/locationaware/LocationServer make all ; make full
this should load it up. note that this is a bad idea on city, as there is still not enough ram to run it there. this will do a full load of the files.
Yep, run it on graphics.
so: should i kill all the rmi procs? how to restart?
I tried to explain this before, but didn't do a great job. The web interface (a java applet) gets the server url from a variable embedded in the <APPLET> tag in the actual web page. View source on the page with the applet to see this for yourself -- I believe the variable is actually called locationServer.
The issue is that Java applets cannot connect to servers at arbitrary URLs ... in fact, they can only connect to localhost! (This is part of the Java Applet security spec -- the presumption is that if you go to some webpage, you trust that page's domain ... but not necessarily some other, unrelated domain.) So, the url in the applet page is just 'localhost'. This is why, if the mitquest stuff is hosted on city, the locationserver must also be running on city. Ditto for graphics.
Does that make sense?
-Patrick
On Sun, 8 Feb 2004, Seth Teller wrote:
ok. so which machine can i start it on? graphics?
how does the web interface know which server should receive its queries ?