Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Sender: mail@stefan-seelmann.de
Date: Wed, 24 Nov 2010 08:58:30 +0100
Message-ID: <AANLkTinZYpCLw2e4LViKaJRJ8b+jTE2ay4D35qk-SSeS@mail.gmail.com>
Subject: Many threads started by Ehcache when running core-integ
From: Stefan Seelmann <seelmann@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi guys,

I had (and still have) problems running the core-integ tests on a
Windows 7 VM. A first analysis using jvisualvm showed that for each
test two new threads were started from Ehcache and never stopped. The
cause is that for each new DirectoryService instance a new
CacheManager is created in CacheService.

To solve that problem I tried to to call CacheManager.shutdown() in
CacheService.destroy(). However then the DNFactory didn't work any
more because it uses a static reference to the cache and that could be
a shutted down instance.

So the next step was to transform the static DNFactory. I renamed
DNFactory to DefaultDNFactory, extracted an DNFactory interface and
removed some unused methods. The DNFactory is now an instance of the
directory service and managed by the directory service. A consequence
is that some test classes can't use the DNFactory any more because it
needs to be initialized by the DirectoryService.

In the end we still create a new CacheManager (which starts its two
threads) for each test but the threads are stopped after each test.

Kind Regards,
Stefan