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

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

We are using ConcurrentHashMap also at other places, should we replace all of 
them or where is the bug that this happens only here?

It also appears to happen on Mike's machine, so maybe its hardware-related 
(Solaris?) as the Sun bugreport seems to tell us.

I am also +0 to apply the patch. I just showed one possibility how to fix this.
                
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to