From users-return-975-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue Oct 10 20:57:20 2006 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 23216 invoked from network); 10 Oct 2006 20:57:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Oct 2006 20:57:20 -0000 Received: (qmail 48094 invoked by uid 500); 10 Oct 2006 20:57:19 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 48082 invoked by uid 500); 10 Oct 2006 20:57:19 -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 48073 invoked by uid 99); 10 Oct 2006 20:57:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2006 13:57:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [66.46.21.156] (HELO smtp.tirawireless.com) (66.46.21.156) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2006 13:57:17 -0700 Received: from localhost (unknown [127.0.0.1]) by smtp.tirawireless.com (Postfix) with ESMTP id 27C3AD002E for ; Tue, 10 Oct 2006 16:56:55 -0400 (EDT) Received: from smtp.tirawireless.com ([127.0.0.1]) by localhost (smtp.tirawireless.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czZAEHIEXCsW for ; Tue, 10 Oct 2006 16:56:48 -0400 (EDT) Received: from scooby.corp.bspark.com (gateway.tirawireless.com [66.46.41.93]) by smtp.tirawireless.com (Postfix) with ESMTP id B2CBCD002C for ; Tue, 10 Oct 2006 16:56:48 -0400 (EDT) x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Tomcat crashed with mode 2 configuration Date: Tue, 10 Oct 2006 16:56:47 -0400 Message-ID: <32FDE2934790A148B7760FDD7843C27906B99C21@exchange.tirawireless.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Tomcat crashed with mode 2 configuration Thread-Index: AcboDgiyYJ0RSp5OSUKKprmJOLGq1gEcRKzw From: "Qun Gu" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Behi, Thanks for your reply. I have checked the MD5 checksums of all the = downloaded JAR files and they are all fine. Thanks for sharing the = trick. :-) I have made a little progress by changing the resource configuration in = Tomcat 4.X way like this: factory = org.apache.jackrabbit.core.jndi.BindableRepositoryFactory configFilePath = c:/dev/apps/tomcat/tomcat-5.5.17/shared/repository/repository.xml<= /value> repHomeDir c:/dev/apps/tomcat/tomcat-5.5.17/shared/repository =20 Tomcat doesn't crash now but I am getting: Oct 10, 2006 4:44:40 PM = org.apache.catalina.mbeans.GlobalResourcesLifecycleListener createMBeans SEVERE: Exception processing Global JNDI Resources javax.naming.NamingException: Cannot create resource instance at = org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFacto= ry.java:142) at = javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at = org.apache.naming.NamingContext.lookup(NamingContext.java:792) at = org.apache.naming.NamingContext.lookup(NamingContext.java:139) at = org.apache.naming.NamingContextBindingsEnumeration.nextElementInternal(Na= mingContextBindingsEnumeration.java:112) at = org.apache.naming.NamingContextBindingsEnumeration.next(NamingContextBind= ingsEnumeration.java:70) at = org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(= GlobalResourcesLifecycleListener.java:136) at = org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(= GlobalResourcesLifecycleListener.java:143) at = org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(= GlobalResourcesLifecycleListener.java:108) at = org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEven= t(GlobalResourcesLifecycleListener.java:80) at = org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSup= port.java:119) at = org.apache.catalina.core.StandardServer.start(StandardServer.java:702) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :39) at = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at = org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) jackrabbit-core-1.0.1.jar file and all the dependencies were already = placed under [Tomcat folder]/common/lib. Any clue on that? Thanks in advance. Best Regards, Qun -----Original Message----- From: behrangsa [mailto:behrangsa@gmail.com] Sent: Wednesday, October 04, 2006 7:37 PM To: users@jackrabbit.apache.org Subject: Re: Tomcat crashed with mode 2 configuration Hi, I have experienced such behaviour previously with other libraries, etc. = For me, it turned out that one of my JAR files had been corrupted during download or build time. I suggest you check the MD5 checksum of your JAR files with what is provided on the Jackrabbit website (I preassume the checksums are available on Jackrabbit's homepage...) Regards, Behi Qun Gu wrote: >=20 > Hi, >=20 > Tomcat 5.5.17 crashed right away after adding the following snippet to > conf/server.xml >=20 > > ...=09 > auth=3D"Container" > type=3D"javax.jcr.Repository" > =09 > factory=3D"org.apache.jackrabbit.core.jndi.BindableRepositoryFactory" > =09 > = configFilePath=3D"c:/dev/apps/tomcat/tomcat-5.5.17/shared/repository/repo= sitory.xml" > = repHomeDir=3D"c:/dev/apps/tomcat/tomcat-5.5.17/shared/repository" > /> > ... > >=20 > I looked through the mailing list and couldn't find a workaround. = Besides, > I couldn't even see the error messages on the console because it = closed so > quick(nothing logged in catalina.2006-10-04.log either). Is there a = way > that I can see the error message? >=20 > Thanks. >=20 > Qun >=20 >=20 >=20 >=20 >=20 --=20 View this message in context: = http://www.nabble.com/Tomcat-crashed-with-mode-2-configuration-tf2383464.= html#a6650323 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.