Troubleshooting

When the applet fails to start:
  1. Make sure that your web browser really runs the next generation Java plug-in and not the legacy Java plug-in.

    For Windows and Mac OSX the procedure is straight forward. Some steps are given below for installing the Java plug-in on Linux:

    Installing the Java plugin in Ubuntu:
    sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
    sudo apt-get update
    sudo apt-get install sun-java6-jdk
    sudo apt-get install sun-java6-plugin

    Manual Installation and Registration of Java Plugin for Linux: http://www.oracle.com/technetwork/java/javase/manual-plugin-install-linux-136395.html

  2. Refresh the web page.
  3. Remove the Java Webstart cache from the local drive and try again.
    • On Windows this folder is located in: %APPDATA%\LocalLow\Sun\Java\Deployment\cache;
    • On Mac OSX this folder is located in: /Users/user_name/Library/Caches/Java/cache;
    • On Linux this folder is located in: /home/user/.java/deployment/cache.
  4. Remove the Author Applet Frameworks cache from the local drive and try again:
    • On Windows Vista or 7 this folder is located in: %APPDATA%\Roaming\com.oxygenxml.author.component;
    • On Windows XP this folder is located in: %APPDATA%\com.oxygenxml.author.component;
    • On Mac OSX this folder is located in: /Users/user_name/Library/Preferences/com.oxygenxml.author.component;
    • On Linux this folder is located in: /home/user/.com.oxygenxml.author.component.
  5. Problems sometimes occur after upgrading the web browser and/or the JavaTM runtime. Redeploy the applet on the server by running ANT in your Author Component project. However, doing this does not always fix the problem, which often lies in the web browser and/or in the Java plug-in itself.
  6. Sometimes when the HTTP connection is slow on first time uses the JVM would simply shut down while the jars were being pushed to the local cache (i.e., first time uses). This shut down typically occurs while handling oxygen.jar. One of the reasons could be that some browsers (Firefox for example) implement some form of "Plugin hang detector" See https://developer.mozilla.org/en/Plugins/Out_of_process_plugins/The_plugin_hang_detector.
Enable JavaWebstart logging on your computer to get additional debug information:
  1. Open a console and run javaws -viewer;
  2. In the Advanced tab, expand the Debugging category and check all boxes.
  3. Expand the Java console category and choose Show console.
  4. Save settings.
  5. After running the applet, you will find the log files in:
    • On Windows this folder is located in: %APPDATA%\LocalLow\Sun\Java\Deployment\log;
    • On Mac OSX this folder is located in: /Users/user_name/Library/Caches/Java/log;
    • On Linux this folder is located in: /home/user/.java/deployment/log.