[ 
https://issues.apache.org/jira/browse/LUCENE-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-5612:
----------------------------------

    Attachment: LUCENE-5612-more-sophisticated-crusher.patch

More improvements:
- Removed the whole "host" parameter (partly unused). As we bind and listen on 
127.0.0.1 there is no need to pass the host to the lock verifier.
- Removed the sleep from ANT. The client checks the port before starting to 
hammer.
- Improved SoTimeouts: Server waits for the *first* connection a maximum of 30 
secs, for all following connections he only waits a much shorter time, 100ms. 
If no more connection arrives, die silently.

> 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
>
>         Attachments: LUCENE-5612-instant-crush.patch, 
> LUCENE-5612-instant-crush.patch, 
> LUCENE-5612-more-sophisticated-crusher.patch, 
> LUCENE-5612-more-sophisticated-crusher.patch, 
> LUCENE-5612-more-sophisticated-crusher.patch, LUCENE-5612-tester.patch, 
> LUCENE-5612-tester.patch, LUCENE-5612.patch
>
>
> 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]

Reply via email to