Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 12619 invoked from network); 22 Feb 2008 09:29:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2008 09:29:00 -0000 Received: (qmail 78598 invoked by uid 500); 22 Feb 2008 09:28:53 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 78526 invoked by uid 500); 22 Feb 2008 09:28:53 -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 78509 invoked by uid 99); 22 Feb 2008 09:28:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 01:28:53 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [62.73.241.56] (HELO mta.tdcsong.no) (62.73.241.56) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 09:28:19 +0000 Received: from [10.10.10.18] (unknown [85.19.194.218]) by mta.tdcsong.no (Postfix) with ESMTP id 8844240F9 for ; Fri, 22 Feb 2008 10:28:24 +0100 (CET) Message-ID: <47BE959F.3070001@corporater.com> Date: Fri, 22 Feb 2008 10:27:59 +0100 From: Audun Landsvik User-Agent: Thunderbird 1.5.0.12 (X11/20080213) MIME-Version: 1.0 To: users@jackrabbit.apache.org Subject: repairing broken definitionIds Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am using Jackrabbit 1.4 (with Jackrabbit core 1.4.1) in a web application. When the server starts and the nodes (and properties) are read from the database, the following warning is printed to the console: WARN [main] (JCLLoggerAdapter.java:268) - property at /default/mzf:Model/mzf:CPeriod/mzf:children[4]/mzf:id has invalid definitionId (1002811280) The warning is sensible enough, as the node type definitions for the nodes have changed since the nodes were stored in the database. The problem is that the database contains thousands of nodes and properties with invalid definitionIds, so the logs are filled with warning messages. Is there a way to repair the definitionIds of nodes and properties in the database without recreating the nodes? regards, AudunL