Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of stefan.guggisberg@gmail.com
 designates 64.233.184.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=MYvjmxtAzynXwIrAONmhN3OZkSLXYiHPgPs6FQrSNWrb/O/IrhSKj8Y5+Ea8YwPczW0RWHwbH8CwzYB5TuTiL+NaH/1uZ1gcxXFCEqtMiHzLzD1CNn8X72XkrGbFU1qWbyPKDTXgLZSZBsmQXtiTe0F4dDwNSJRa2J/pl2bIDkU=
Message-ID: <90a8d1c00603270500t2eaf3082y821e4b6b9dac9855@mail.gmail.com>
Date: Mon, 27 Mar 2006 15:00:41 +0200
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: Strange non-failure error during unit testing
In-Reply-To: <A596BB65-1097-4488-ADAD-E95D0A81D62B@analogsoftware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <A596BB65-1097-4488-ADAD-E95D0A81D62B@analogsoftware.com>

hi mark
thanks for reporting this issue! it's indeed a bug. i fixed it in
svn r389129.

cheers
stefan

On 3/25/06, Mark Slater <mark@analogsoftware.com> wrote:
> I'm not sure if this matters (as in, for all I know, its a hiccup in
> the JVM and nothing to do with Jackrabbit at all), but I just got a
> very strange error in the test phase of the build process:
>
>      [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed:
> 0.359 sec
>      [junit] Running org.apache.jackrabbit.test.api.lock.TestAll
>      [junit] Tests run: 23, Failures: 0, Errors: 0, Time elapsed:
> 6.813 sec
>      [junit] Exception in thread "Thread-4"
> java.util.NoSuchElementException
>      [junit]     at
> org.apache.commons.collections.map.AbstractReferenceMap
> $ReferenceEntrySetIterator.nextEntry(AbstractReferenceMap.java:772)
>      [junit]     at
> org.apache.commons.collections.map.AbstractReferenceMap
> $ReferenceValuesIterator.next(AbstractReferenceMap.java:829)
>      [junit]     at org.apache.jackrabbit.core.RepositoryImpl.shutdown
> (RepositoryImpl.java:858)
>      [junit]     at
> org.apache.jackrabbit.core.jndi.BindableRepository.shutdown
> (BindableRepository.java:257)
>      [junit]     at org.apache.jackrabbit.core.jndi.BindableRepository
> $1.run(BindableRepository.java:133)
>      [junit] Running org.apache.jackrabbit.test.api.nodetype.TestAll
>      [junit] Tests run: 99, Failures: 0, Errors: 0, Time elapsed:
> 24.768 sec
>      [junit] Running org.apache.jackrabbit.test.api.observation.TestAll
>      [junit] Tests run: 40, Failures: 0, Errors: 0, Time elapsed:
> 10.539 sec
>
> There were no errors that I could find before this, or after it, and
> no mention was made of it in any JUnit output files or log files that
> I could find. At the end, maven reported a successful build.
>
> I'm not particularly worried about it... a build I did just a few
> minutes before had no errors. The only thing that changed between the
> two was the removal of some logging statements in
> CustomNodeTypeConfig (I was trying to track down a null input stream
> exception).
>
> On one hand I thought about dismissing this out of hand since it
> doesn't seem to be reproducible (I tried a few times), but on the
> other, some of the nastiest bugs I've ever had to track down were
> sporadic and only showed up once in a very long while.
>
> Mark
>