Return-Path: 
 <users-return-46351-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5F5DC101B8
	for <apmail-camel-users-archive@www.apache.org>;
 Wed, 22 Jan 2014 16:40:07 +0000 (UTC)
Received: (qmail 42788 invoked by uid 500); 22 Jan 2014 16:40:04 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 42753 invoked by uid 500); 22 Jan 2014 16:40:03 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 42644 invoked by uid 99); 22 Jan 2014 16:39:59 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 16:39:59 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of sburkard@gmail.com designates
 209.85.214.174 as permitted sender)
Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com)
 (209.85.214.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 16:39:52 +0000
Received: by mail-ob0-f174.google.com with SMTP id uy5so690592obc.19
        for <users@camel.apache.org>; Wed, 22 Jan 2014 08:39:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=fHwrSlpS16MG3T8tuRjAFVIE4ik7iFNjubxsr5ah6Us=;
        b=XdEsVh5YghqmuuF1QJqGfntsn3WChYq0+yN0sQjRMhde/TMTMRGCtCscpIbMwh9JRS
         9J6F7ff0cig5DlflcaLMgxGdD0DXtwKxz2LRiDXhNpWDeJFXfmmh7mTp8yiS+BgF4ru/
         671M2Nbs9vVCjhzrofV6xtF4dKaVQK9hbWO6hmrxT+xvY1VgJRayDi/gV0i9pI5rq3u/
         vaGzVO3NRrXIND1HlpOgfvQ580fklXaGCHSP8srLijw+KI9byPi71DniICg2iBFKxptl
         OGejFDfi+aJMs2mqCbYkOMq7CrAoLOEEtRRRhdlkBOWN0Q4PZuLzmeKKeC7kxh22On5Q
         7ygw==
MIME-Version: 1.0
X-Received: by 10.182.48.130 with SMTP id l2mr2141217obn.44.1390408771337;
 Wed, 22 Jan 2014 08:39:31 -0800 (PST)
Received: by 10.76.72.74 with HTTP; Wed, 22 Jan 2014 08:39:31 -0800 (PST)
In-Reply-To: 
 <CABctVUjv12ctThsNXwUjR28A6HoEH=yOBBHMnQ-Q1dPVuiZb9A@mail.gmail.com>
References: 
 <CABctVUjv12ctThsNXwUjR28A6HoEH=yOBBHMnQ-Q1dPVuiZb9A@mail.gmail.com>
Date: Wed, 22 Jan 2014 17:39:31 +0100
Message-ID: 
 <CABctVUigg4r3daFdotwLGpSt7XjWXQ=6BfySwik7yJNaT2CJdw@mail.gmail.com>
Subject: Re: LevelDB and Route-Tests
From: Stephan Burkard <sburkard@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=089e0160b3dce8856904f091c4ad
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0160b3dce8856904f091c4ad
Content-Type: text/plain; charset=UTF-8

OK, what I found out until now:

- All test classes of the Camel LevelDB component contain only 1 Test
- The POM of the component contains a surefire config
"<forkMode>pertest</forkMode>"
  => what means the same as "<forkMode>always</forkMode>"
  => what means "fork for each test-class" (yes, the term "pertest" is very
confusing)

Therefore I guess the developers of the component had the same problems.

But that means that in Eclipse only 1 Test can run in the same test-run,
because the JUnit-Testrunner of Eclipse has no configuration to fork the
tests.

Stephan




On Tue, Jan 21, 2014 at 1:04 PM, Stephan Burkard <sburkard@gmail.com> wrote:

> Hi Camel users
>
> I ran into another problem with the LevelDB aggregator persistence. The
> error I get is "Error opening LevelDB with file [path to
> persistentFileName]". The cause of it is "LOCK: already held by process".
>
> This happens when I run multiple route tests using CamelSpringTestSupport.
>
> The individual tests run fine, if they run in the same test-run, the first
> succeeds and the rest fails with the error above.
>
> Since the Camel context is restarted per test, I also remove the whole
> directory with the levelDB file in the @Before method of my test-classes,
> so that the DB is "blank" for every test method.
>
> Is this a wrong behaviour for the tests? What is the best practice to have
> a new LevelDB for every test case.
>
> Thanks for any help
> Stephan
>
>

--089e0160b3dce8856904f091c4ad--