On Oct 24, 2007, at 2:33 AM, sbyonge wrote:

<snip>

Found one Java-level deadlock:
=============================
"Finalizer":
  waiting to lock monitor 0x01807a70 (object 0x06a73370, a
sun.misc.Launcher$AppClassLoader),
  which is held by "main"
"main":
  waiting to lock monitor 0x01807a94 (object 0x0a584ae8, a [[I),
  which is held by "Finalizer"

Java stack information for the threads listed above:
===================================================
"Finalizer":
        at
org.apache.geronimo.transformer.TransformerCollection.transform (TransformerCollection.java:35) at sun.instrument.TransformerManager.transform (TransformerManager.java:122)
        at
sun.instrument.InstrumentationImpl.transform (InstrumentationImpl.java:155)
        at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:82)
        at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
"main":
        at java.lang.ClassLoader.findBootstrapClass(Native Method)
        at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
        - locked <0x06a75730> (a sun.misc.Launcher$ExtClassLoader)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
        - locked <0x06a73370> (a sun.misc.Launcher$AppClassLoader)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        - locked <0x06a73370> (a sun.misc.Launcher$AppClassLoader)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        - locked <0x06a73370> (a sun.misc.Launcher$AppClassLoader)

Found 1 deadlock.

Thanks.

OK. We've seen this problem before (but not on a mac, at least not that I've seen...). IMO this is a JRE bug -- http://bugs.sun.com/ bugdatabase/view_bug.do?bug_id=5088398

We worked around the issue and seems to be working in other environments -- https://issues.apache.org/jira/browse/GERONIMO-3141

I've never seen this problem on my intel MacBook Pro -- a bit curious about how you can reproduce so easily... Meantime will see how else we can work-around...

--kevan

Reply via email to