This appendix includes the following information:
Following are some common problems that you may encounter when using Java Plug-in for Solaris. For additional information, consult the Java Plug-in FAQ.
Java Plug-in does not recognize Netscape Navigator settings -- Java Plug-in reads Navigator's settings when it starts. If you make any changes to Navigator settings, you must restart Navigator for Java Plug-in to recognize the new settings.
You cannot restart the Java Plug-in Console -- If you close Java Plug-in Console, you must close and then restart Netscape in order to restart the Console.
You encounter a web page containing a Java Plug-in applet that says you do not have the appropriate plug-in installed -- First, verify that you correctly set all environment variables. Then, make sure all MIME types are enabled by choosing About Plug-ins from the Help menu.
Cookies are not accessible when you use Java Plug-in with a protected server -- Most mechanisms used to enable protected directories on the web server use cookies. However, Java Plug-in does not provide cookie support. Although you can log in to your web server and generate a cookie with Navigator, the cookie is not accessible by Java Plug-in.
You experience problems when rendering an applet -- When an applet is loaded on a web page that specifies Java Plug-in, a SecurityException is triggered. In order to perform certain security checks, the Applet Security Manager must find the IP address from which your applet was downloaded. If your network does not support Domain Name Service (DNS), these security checks may fail. To correct this problem, specify an IP address rather than a host name in the URL when visiting the target web page.
You set the JAVA_PLUGIN_TRACE environment variable to display Java instructions as they are executed within an applet. By default, this tracing information appears in Netscape Alert Panels.
To direct the tracing output to your terminal window, see "Directing Tracing Output to a Terminal Window".
Type the command for the appropriate shell.
Table A-1 Displaying Tracing OutputShell | Command |
---|---|
csh | % setenv java_plugin_trace |
sh or ksh | % java_plugin_trace="" |
% export java_plugin_trace |
You can direct tracing output to:
your terminal window
the terminal window of each user on a multi-user system
Edit your ~/.Xdefaults file , changing the following lines from True to False.
*useStderrDialog: False
*useStdoutDialog: False
Reload resources by typing xrdb -merge .Xdefaults at the prompt.
Edit the Netscape resource file /<installation directory>/lib/locale/C/app-defaults/Netscape, changing the following lines from True to False.
*useStderrDialog: False
*useStdoutDialog: False
Stop and then restart Netscape.
You enable the Show Java Console option on the Java Plug-in Console (see "Basic Tab") to view error messages generated by Java Plug-in. When you visit a Java Plug-in-enabled page and encounter an error, the Java Plug-in Console opens, showing the error output. All output written to the Java System.err or System.out streams is written to the Console window.
If you set the JAVA_PLUGIN_TRACE environment variable but do not enable the Java Console (see "Java Plug-in Control Panel"), error messages appear in Netscape Alert Panels with the tracing information.
If you set the JAVA_PLUGIN_TRACE environment variable and enable the Java Plug-in Console, Java Plug-in's Java code also displays in the Console window (each line starts with Java:), and the C/C++ code displays in Netscape Alert panels (each line starts with Plugin:).
To report bugs, contact your Solaris service provider. When reporting a bug, include the following:
Version number of Solaris
Version number of Netscape Navigator
Complete output of the Java Console window
Java Plug-in tracing information
Your network configuration information, including proxy, special intranet environment, etc.
A complete description of the problem including any sample applets that demonstrate the problem, and the steps you took to reproduce the problem