[
https://issues.apache.org/jira/browse/LUCENE-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972793#comment-13972793
]
Uwe Schindler edited comment on LUCENE-5612 at 4/17/14 9:52 AM:
----------------------------------------------------------------
OK, I delay the release!
We can add a test case, if we do it in the same way like
TestIndexwriterOnJRECr*u*sh (spawn 2 VMs). I would not do this in smoke tester,
as this should be tested with our test suite. We should also test the other
lock factories with this approach.
Smoke tester is not enough, because it does not work on Windows, so we
definitely have to test this in our default test suite. I will try
NativeLockFactory now on Windows.
was (Author: thetaphi):
OK, I delay the release!
We can add a test case, if we do it in the same way like
TestIndexwriterOnJRECr*u*sh (spawn 2 VMs). I would not do this in smoke tester,
as this should be tested with our test suite. We should also test the other
lock factories with this approach.
> LockStressTest fails always with NativeFSLockFactory
> ----------------------------------------------------
>
> Key: LUCENE-5612
> URL: https://issues.apache.org/jira/browse/LUCENE-5612
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Blocker
> Fix For: 4.8
>
>
> I was looking at this, because i wanted to remove the static map inside
> NativeFSLockFactory (no particular reason: it just smells bad, we require
> java7, and you get overlappingexception as of java6 so its unnecessary).
> Before changing any code, i wanted to run lockstresstest first, just to
> ensure it works: but it fails always. Simple works fine always.
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.RuntimeException: lock was double acquired at
> org.apache.lucene.store.VerifyingLockFactory$CheckedLock.verify(VerifyingLockFactory.java:67)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
