Site Technical Updates


When testing the connection to our server today, I got one of the "file not found" errors that some of the MiRTLE testing has run into. The path mentioned in the error was on the local machine, not the server, and the clients had not been updated recently. This seems to indicate that an update to Java itself (which these machines have had) rearranged the directory structure and/or naming of libraries somewhat, and Wonderland isn't smart enough to figure out where they went.


Perhaps not...

After restarting the server, the clients are still showing error messages in their console output while starting, but seem to be connecting fine again, so those must not be fatal. I guess the server had an unclean start of some kind instead. It would be really nice if Solaris had more intelligent ways of running such things...