-
Notifications
You must be signed in to change notification settings - Fork 6
Troubleshooting
NOTE: due to Oracle's new licensing scheme we recommend that you build and install the foraging software with openjdk instead of the Oracle JDK. The foraging application should work properly with openjdk and IcedTea's WebStart implementation. We have not tested openwebstart thoroughly yet. The instructions below are for the Oracle JDK, you will still need to "trust" the server that is deploying your client and facilitator jar files but you should be able to do so from the IcedTea OpenJDK window that starts when you try to open the client or facilitator JNLP file.
In order to run Java WebStart applications you will need to add your experiment server address to the Java Site Exception List for each client computer.
- Bring up the Java Control Panel (Windows, Mac, Linux)
- Click on the
Security
tab - Click the
Edit Site List
towards the bottom right corner of the tab - Click the
Add
button - Enter your
server.address
including the http:// or https:// protocol, e.g., http://example.com:8080 and clickOK
- You'll see a warning if you used http:// - click OK to ignore it.
- Click OK to close the control panel. While you are there you may want to enable the Java console on a few client computers to help debug by clicking to the
Advanced
tab and select theShow console
radio button underJava console
.
This is usually an issue with the webserver serving the images.
If you are serving the JNLP files and images over https you will need to explicitly set the codebase.url
property in your build.properties
file to https://yourservername.example.com/foraging
or whatever URL is serving the foraging client and facilitator assets.
if using chromium-browser
and the browser is opening but not the correct URL, you may need to check ~/.local/share/applications/chromium-browser.desktop
and verify that the Exec=chromium-browser
line has a %U
at the end to pass in the parameterized URL.