Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 15 Nov 2011 15:14:51 +0000 (UTC)
From: "Mark Miller (Commented) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1052424424.31147.1321370091664.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1742638795.34385.1308859007529.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (LUCENE-3235) TestDoubleBarrelLRUCache hangs
 under Java 1.5, 3.x and trunk, likely JVM bug
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mark Miller commented on LUCENE-3235:
-------------------------------------

bq. I still think the workaround (scoped down to 1.5, Sun JVM, little endian arch) makes sense?

+1 Doesn't hurt other JVMs, improves things on the Sun JVM (something that hangs a lot and then does not hang is a big improvement in my book), and putting a workaround command to use in the wiki just seems a whole lot less user friendly to me. It doesn't mean we have to try and address every use of java.util.concurrent to work around this specific issue, does it?
                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org