A customer (see Comments for contact details) provided a test case that shows that the recent fix for 6683047 (separate_jvm parameter should tear down target JVM more quickly) is conflicting with the applet relaunch mechanism. The attached JVM is tearing itself immediately after sending the applet relaunch message back to the browser and the browser side never gets a chance to process it. The code needs to be changed so that the browser side is responsible for tearing down the attached JVM in the case where the attached JVM was for a particular applet and it also caused an applet relaunch.