lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3235) TestDoubleBarrelLRUCache hangs under Java 1.5, 3.x and trunk, likely JVM bug
Date Tue, 15 Nov 2011 21:57:51 GMT

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

Robert Muir commented on LUCENE-3235:
-------------------------------------

{quote}
How are we slowing down other VMs...? We scope the workaround?
{quote}

I agree, according to the bug report it seems all 1.5's are affected and some 1.6's?
Doesn't seem like solaris is related either, especially since Mike hit it on linux

So the current patch is actually way under-scoped.

Sure, some 1.6's are affected, and if we want it to be even better,
we should likely improve Constants a little bit to make the minor
version more easily accessible, from the bug report it seems we
should at least consider doing something for < 1.6.0u21 ? And we should
remove the 'Solaris' check, but keep it little-endian because the bug
report mentions its way more likely to happen on those cpus.

                
> 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


Mime
View raw message