Documentation Contents
Java Platform, Standard Edition Troubleshooting Guide
Contents    Previous    Next

16.2 Troubleshoot Applets

For modern browsers which support tabs, each tab might be a separate browser process. If a Java applet is embedded in a browser page and the next generation plugin is being used, usually the process associated with the browser tab creates a JVM within the process (browser VM). The browser VM will create another JVM process (client VM) which will run the applet and manage the applet's life cycle. The client VM is a Java process (java.exe on Windows and java on Oracle Solaris/Linux platforms).

The following are some problems with Applets and troubleshooting techniques.

16.2.1 Plugin Cheat Sheet for Applet Start

If your applet does not start, make sure to enable tracing and the Java console as explained previously. Then use hits below to find reason why applet does not work.

Do you get a trace file generated or see the Java console?

    • No, I don't get a trace file

      Check if Java technology is detected, see

      • Yes

        Look at JVM browser issues from

      • No

        It is likely to be a configuration issue. See for common configuration problems and if it does not help, look at JVM browser issues from

    • Yes, I have a trace file

      It is unlikely to be a configuration issue (unless you have the new generation plugin disabled). The problem is likely to be specific to this applet. Try to launch some other applets to confirm. Look at JVM client issues from

16.2.2 Browser or Java Process Crash

A crash could be caused by a platform or application issue.

Typically, if a crash happens in the JVM then there should be hs_err_*log file created in the current working directory (on Windows it is often placed on the desktop). It is the same crash report file as for standalone applications. For details about the report file, see Appendix A.

If you can spot native libraries loaded from the deployment cache directory, especially if you see code from these libraries in the crash stack, it is very likely to be a bug in the application.

Otherwise it is a JRE bug and needs to be reported to Bug Database.

The following are two scenarios to consider for a crash by platform or application issue.

16.2.3 Unresponsive Web page

The following are scenarios that could cause an unresponsive web page.

Contents    Previous    Next

Oracle and/or its affiliates Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.
Contact Us