Name: gm110360 Date: 03/24/2003


FULL PRODUCT VERSION :
1.3.1_04
1.4.1_01

FULL OS VERSION :
Microsoft Windows 2000, Microsoft XP Professional

EXTRA RELEVANT SYSTEM CONFIGURATION :
IE 5.5
IE 6.0 (6.0.2800.1106.xpsp1.020828-1920IC)
Netscape 6.2+ (not personally verified but reported by a client)

A DESCRIPTION OF THE PROBLEM :
It appears that when you go from the 1.3.1 page and then go to the 1.4.1 plug-in based page the 1.4.1 plugin attempts to hook onto the 1.3.1 VM. I would of expected to see a new 1.4.1 VM be started (with no errors, obviously).

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Try this:
Test - Java Plug-in 1.3.1 to a Java Plug-in 1.4.1 page
Step 1 - Open a new browser window to http://192.18.97.35/products/plugin/1.3/demos/applets/ArcTest/example1.html
Step 2 - In that same browser window go to http://java.sun.com/products/plugin/1.4.1/demos/plugin/applets/ArcTest/example1.html

You'll receive the following error:
Title: "Java(TM) Plug-in Fatal Error"
Message: "Attachment to a running Virtual Machine failed"


  To further show the errors that occur when trying to load multiple plug-in VMs try the reverse.

Test - Java Plug-in 1.4.1 to a Java Plug-in 1.3.1 page
Step 1 - Open the 1.4.1 url in a new browser window. (http://java.sun.com/products/plugin/1.4.1/demos/plugin/applets/ArcTest/example1.html)
Step 2 - Now, in the same window, navigate to the 1.3.1 site.
(http://192.18.97.35/products/plugin/1.3/demos/applets/ArcTest/example1.html)

You'll receive another error message this one appearing to be uglier than before.
Title: "Microsoft Visual C++ Runtime Library"
Message: "Runtime Error!
          Program: C:\Program Files\Internet Explorer\iexplore.exe

abnormal program termination."

EXPECTED VERSUS ACTUAL BEHAVIOR :
Would of expected in the first test a 1.4.1 VM to be initiated and in the second test a 1.3.1_04 VM to be started.
Received error message and immediate browser crash.


ERROR MESSAGES/STACK TRACES THAT OCCUR :
Title: "Java(TM) Plug-in Fatal Error"
Message: "Attachment to a running Virtual Machine failed"

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Only work around is to use like VMs which is far from a solution since in our situation we have no control on one of the VMs being used.
(Review ID: 182103)
======================================================================