[RFC] [Plugin] Fixes 100% cpu load

[Andrew Su]

Hello,

This patch fixes the following:
*Plugin goes into a deadlock waiting for another thread to initialize applet, and no more threads are available to consume messages.
*Plugin handles "destroy" message when another thread trying to create the applet is kicked off processor before setting the status to PRE_INIT.


Example.
We have 2 MessageConsumer threads.
Passes "destroy" message to both of them for applet 1 and applet 2.
Thread 1: Spinlock waiting for another thread to initialize applet 1.
Thread 2: Spinlock waiting for another thread to initialize applet 2.
Both threads are now in deadlock.

Proposed Patch:
When message is destroy, don't spinlock, handle it right away.
-Problem with this: handles destroy right before we start initializing the applet.
-Fix to new problem: Synchronize the two blocks
--Case 1:If in process of initializing, finish initializing. handle the destroy.
--Case 2:If destroy already handled, don't initialize.


Cheers,
  Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20100927_destroy_deadlock.patch
Type: text/x-patch
Size: 7959 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20100927/3b08d62d/20100927_destroy_deadlock.patch