title: Strange thread dump on deadlock
body: <p>We've been experiencing a strange deadlock during the startup of our java application.  When I run jstack on the application to investigate, I see that the AWT-EventQueue is in Object.wait(), but the thread is still marked as RUNNABLE.  I've included the relevent parts of the thread dump, and I'm hoping that someone can shed some light on this issue. </p>
  
  <pre><code>"AWT-EventQueue-0" prio=6 tid=0x5f0a2400 nid=0x19e4 in Object.wait() [0x6007e000]
         java.lang.Thread.State: RUNNABLE
          at com.ge.med.platinum.work.isu.ExamTransaction.getEAOTableLite(ExamTransaction.java:1514)
            ...
            - locked &lt;0x1fc87448&gt; (a java.awt.Component$AWTTreeLock)
            ...
  
  "Thread-63-Pool-9" prio=6 tid=0x5f1a2800 nid=0x1f54 waiting for monitor entry [0x61a9f000]
     java.lang.Thread.State: BLOCKED (on object monitor)
      at java.awt.Component.setFont(Component.java:1777)
      - waiting to lock &lt;0x1fc87448&gt; (a java.awt.Component$AWTTreeLock)
        ...
  
  "Thread-289-Pool-3" prio=6 tid=0x60afe800 nid=0x12b8 waiting for monitor entry [0x623fe000]
     java.lang.Thread.State: BLOCKED (on object monitor)
      at java.awt.Component.setFont(Component.java:1777)
      - waiting to lock &lt;0x1fc87448&gt; (a java.awt.Component$AWTTreeLock)
        ...
  </code></pre>
  
  <p>In addition, I've noticed <a href="https://stackoverflow.com/questions/64989/jvm-thread-dumps-containing-monitors-without-locking-threads">this thread</a>, which mentions that accessing a static variable may be involved.  This is also the case in our application.  The line in getEAOTableLite in question references a static method.</p>