Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9899510568 for ; Mon, 30 Sep 2013 13:56:31 +0000 (UTC) Received: (qmail 62185 invoked by uid 500); 30 Sep 2013 13:56:26 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 62028 invoked by uid 500); 30 Sep 2013 13:56:24 -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 62014 invoked by uid 99); 30 Sep 2013 13:56:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Sep 2013 13:56:24 +0000 Date: Mon, 30 Sep 2013 13:56:24 +0000 (UTC) From: "Unico Hommes (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (JCR-3674) Unwarranted errors logged about nodetype registrations in a clustered environment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Unico Hommes created JCR-3674: --------------------------------- Summary: Unwarranted errors logged about nodetype registrations in a clustered environment Key: JCR-3674 URL: https://issues.apache.org/jira/browse/JCR-3674 Project: Jackrabbit Content Repository Issue Type: Bug Reporter: Unico Hommes Assignee: Unico Hommes For instance: 19.09.2013 17:07:51 ERROR [org.apache.jackrabbit.core.cluster.ClusterNode.process():928] Unable to deliver node type operation: {http://www.onehippo.org/jcr/hipposys/nt/1.0.5}updaterinfo already exists locally This happens on cluster node 1 after on cluster node 2 new node types were registered while cluster node 1 was down. When cluster node 1 is brought up again, it first loads the updated node types and afterwards processes the cluster updates from the journal. During the latter process new node types are found to be already cached, which causes the above error. -- This message was sent by Atlassian JIRA (v6.1#6144)