JDK-4358142 : Mime-types not loaded properly on Netscape - intermittent bug
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.3.0
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: solaris_8
  • CPU: x86
  • Submitted: 2000-08-01
  • Updated: 2001-02-05
  • Resolved: 2000-11-27
Description
Version of Java:
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-b24)
Java HotSpot(TM) Client VM (build 1.3.0-b24, mixed mode)

System Information:
SunOS deepesh 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-5_10

Processor Information:
Status of processor 0 as of: 07/31/00 18:05:50
  Processor has been on-line since 07/17/00 20:41:07.
  The sparcv9 processor operates at 440 MHz,
        and has a sparcv9 floating point processor.

STEPS TO REPRODUCE:
- Install build 24 of Kestrel/Solaris on your host solaris machine
  for sparc
  /net/hotvm.eng/export/sail1/jdk1.3_b24/production-1.3-b24/pkgarchive/sparc/b24
  for x86
  /net/hotvm-x.eng/builds/jdk1.3_b24/production-1.3-b24/pkgarchive/i386/b24

- Set the environment variable NPX_PLUGIN_PATH
  for sparc
  % setenv NPX_PLUGIN_PATH "path to build24 jre"/plugin/sparc
  for x86
  % setenv NPX_PLUGIN_PATH "path to build24 jre"/plugin/i386

- Start netscape, select "About Plug-ins" from the "Help" menu.

RESULTS:
Since this is an intermittent failure, sometimes we see only a few mime-types
enabled in the plugin table for "Java(TM) Plug-in 1.3.0-b24". All the mime-types
should have been enabled.
The problem has been noticed in both sparc and x86 solaris 6, 7 & 8. Generally mime-type 1.3, 1.2.2, 1.2.1 and 1.1.3 will be enabled whereas mime-type 1.2, 1.1.2, 1.1.1 and 1.1 will not be enabled.

Comments
WORK AROUND Exiting the browsers and rerunning it is one solution.
11-06-2004

EVALUATION Committed to 1.3.1. This is a Netscape bug/issue. At best we could probably work around it to the point where an individual user wouldn't have to restart, if they installed there own copy of netscape. A user using a common install would still have the problem. This amounts to a non-trival amount of work for very little gain. As such I think we should just live with this, or pressure Netscape to fix the actual probelm. steve.katz@East 2000-11-27
27-11-2000