[ 
https://issues.apache.org/jira/browse/LUCENE-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150561#comment-13150561
 ] 

Uwe Schindler commented on LUCENE-3235:
---------------------------------------

This testcase fails, but we are using concurrent also in ParallelMultiSearcher 
(die, die, die) and other places (even the indexer was partly upgraded to use 
ConcurrentLock). In my opinion we should not change our code to work around 
that issue. Just because one test case hangs its not guaranteed that other uses 
will work correctly. It brings a false security and slows down VMs that work 
correctly. And it only affects very modern processors.

If we would have a logging framework in Lucene (maybe Solr could do this): It 
could parse the args of Java (from system property) and look for 
-XX:+UseMembar, if its Java 1.5 it should print a warning to Solr/Lucene log 
file.
                
> TestDoubleBarrelLRUCache hangs under Java 1.5, 3.x and trunk, likely JVM bug
> ----------------------------------------------------------------------------
>
>                 Key: LUCENE-3235
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3235
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 3.0, 3.1, 3.2, 3.3, 3.4
>            Reporter: Michael McCandless
>             Fix For: 3.5
>
>         Attachments: LUCENE-3235.patch, LUCENE-3235.patch, LUCENE-3235.patch
>
>
> Not sure what's going on yet... but under Java 1.6 it seems not to hang bug 
> under Java 1.5 hangs fairly easily, on Linux.  Java is 1.5.0_22.
> I suspect this is relevant: 
> http://stackoverflow.com/questions/3292577/is-it-possible-for-concurrenthashmap-to-deadlock
>  which refers to this JVM bug 
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6865591 which then refers 
> to this one http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6822370
> It looks like that last bug was fixed in Java 1.6 but not 1.5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to