From dev-return-11963-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon May 14 08:25:45 2007 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 35237 invoked from network); 14 May 2007 08:25:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 May 2007 08:25:44 -0000 Received: (qmail 6467 invoked by uid 500); 14 May 2007 08:25:44 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 6404 invoked by uid 500); 14 May 2007 08:25:43 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 6389 invoked by uid 99); 14 May 2007 08:25:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2007 01:25:43 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2007 01:25:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 99C52714068 for ; Mon, 14 May 2007 01:25:16 -0700 (PDT) Message-ID: <18360082.1179131116626.JavaMail.jira@brutus> Date: Mon, 14 May 2007 01:25:16 -0700 (PDT) From: "Dominique Pfister (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Assigned: (JCR-915) Invalid Journal Record appearing when read during sync operation In-Reply-To: <12750224.1179083475410.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister reassigned JCR-915: ------------------------------------- Assignee: Dominique Pfister > Invalid Journal Record appearing when read during sync operation > ---------------------------------------------------------------- > > Key: JCR-915 > URL: https://issues.apache.org/jira/browse/JCR-915 > Project: Jackrabbit > Issue Type: Bug > Components: core > Affects Versions: 1.3 > Environment: OSX 10.4, JDK 1.5 > Reporter: Ian Boston > Assigned To: Dominique Pfister > > ERROR: Error while processing revision 3161: Unknown entry type: > (a) (2007-05-13 19:57:02,258 main_org.apache.jackrabbit.core.cluster.ClusterNode) > ERROR: Unable to start clustered node, forcing shutdown... (2007-05-13 19:57:02,259 main_org.apache.jackrabbit.core.RepositoryImpl) > org.apache.jackrabbit.core.cluster.ClusterException: Unable to read record with revision: 3161 > at org.apache.jackrabbit.core.cluster.ClusterNode.sync(ClusterNode.java:285) > at org.apache.jackrabbit.core.cluster.ClusterNode.start(ClusterNode.java:229) > at org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java:308) > at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584) > at org.sakaiproject.jcr.jackrabbit.RepositoryBuilder.init(RepositoryBuilder.java:213) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > This is a 2 node cluster, with persistance managers in the DB and journal on the shared filesystem. > Start the first node in the cluster up from a completely clean and empty repo. > Let it add some note types, and create a since workspace (called sakai) and then connect via webdav (using OSX Finder) which creates some Journal Records (due to the finder putting some .xxxx files in) > Dont add any files. > Then start the second node in the cluster up, > It runs through the first 15 or so journal entries and then hits a one where the entry is unknown (stack trace above) > Some analysis to follow -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.