Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 54311 invoked from network); 22 Sep 2009 18:13:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Sep 2009 18:13:16 -0000 Received: (qmail 78749 invoked by uid 500); 22 Sep 2009 18:13:15 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 78701 invoked by uid 500); 22 Sep 2009 18:13:15 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 78690 invoked by uid 99); 22 Sep 2009 18:13:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 18:13:15 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [194.65.62.162] (HELO mailtrq.tranquilidade.pt) (194.65.62.162) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 18:13:06 +0000 Message-ID: <763D7B10-8B5E-4F17-9956-D85FE517A208@pmelink.pt> From: Bruno Coelho To: "users@jackrabbit.apache.org" In-Reply-To: <4AB8F41A.8090205@anyware-tech.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 (Apple Message framework v936) Subject: Re: problem shuting down tomcat Date: Tue, 22 Sep 2009 19:12:40 +0100 References: <5bab330d0909220211o1f1316a9l9f1de4288c83e49f@mail.gmail.com> <7911A7E5-EA4D-4A59-9F18-98EAEFDB966A@pmelink.pt> <4AB8E0DE.9060606@anyware-tech.com> <37554878-564F-48C3-8865-CC010DC955D8@pmelink.pt> <4AB8E754.8060609@anyware-tech.com> <91f3b2650909220809m363b850eg2dcc2587b3f2f133@mail.gmail.com> <8C187711-4FDC-4E45-A523-16DC4126D174@pmelink.pt> <4AB8F41A.8090205@anyware-tech.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org thank you for the info but everything I found there tells me that the =20= problem is related to some reference in the RMI server that is not unbind or unexported =20 properly. I tried the following code in the RepositoryStartupServlet to see if =20 there were some remote object that weren't unbind or unexported but I =20= couldn't find any, I inserted this line after the last line of code in the method =20 unregisterRMI(): try { String[] names =3D registry.list(); log.info("names list lenght: " + names.length); for(int i =3D 0; i < names.length; i++){ try{ log.info("trying to unbind: " + names[i]); registry.unbind(names[i]); log.info("trying to unexport remote obj with =20= name: " + names[i]); Remote remoteobj =3D (Remote) =20 registry.lookup(names[i]); UnicastRemoteObject.unexportObject(remoteobj, =20= true); } catch(Exception ex) { log.error("Exception " + ex); } } } catch (RemoteException re) { log.error("Remote Exception getting list: " + re); } but the list is empty! so at this moment I don't know whatelse to try... is there any other place in the code where are some objects being bind? thanks one more time! cheers, bruno coelho On Sep 22, 2009, at 4:58 PM, S=E9bastien Launay wrote: > Le 22/09/2009 17:29, Bruno Coelho a =E9crit : >> "RMI Reaper" prio=3D5 tid=3D0x0102cfe0 nid=3D0x8d2400 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" =20 > 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-t= he-Reaper-thread-td5661918.html > > -- > S=E9bastien Launay