Le 22/09/2009 17:29, Bruno Coelho a écrit : > "RMI Reaper" prio=5 tid=0x0102cfe0 nid=0x8d2400 in Object.wait() > [0xb1011000..0xb1011d90] > at java.lang.Object.wait(Native Method) > - waiting on <0x29adfdd8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:120) > - locked <0x29adfdd8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:136) > at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:336) > at java.lang.Thread.run(Thread.java:613)
This is the only user thread as it does not contains the "daemon" token. I don't know well how RMI and Jackrabbit works but the RMI connection appears to not be closed leading to this thread still alive. After googling, i find more information here: http://www.nabble.com/Correct-way-of-avoiding-a-shutdown-delay-caused-by-the-Reaper-thread-td5661918.html -- Sébastien Launay
