Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6609036

Add more heartbeats to the system

    Details

    • Subcomponent:
    • Introduced In Build:
      b08
    • Introduced In Version:
    • Resolved In Build:
      b09
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Not verified

      Description

      We have run into a couple of bugs where the main loop in the PluginMain class locked up due to EventQueue.invokeAndWait() being called. In this situation we will be unable to run any more applets in this JVM instance, and the browser will become unresponsive because it will wait several seconds for some message acknowledgments that will never come.

      To guard against this inadvertently happening in the future we should add a per-JVMInstance heartbeat thread similar to that already in the client JVM process. Probably the pauses between the heartbeats should be longer than in the client JVM process, since this is only intended as a measure of last resort. If the browser-side code determines that a given JVMInstance is unresponsive, it should use Process.destroy() to terminate it. The existing code on the browser side will handle the necessary cleanups.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kbr Kenneth Russell (Inactive)
                Reporter:
                kbr Kenneth Russell (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: