db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3604) Hang in .suites.All on 10.4 trunk ('Found one Java-level deadlock')
Date Tue, 08 Feb 2011 00:44:57 GMT

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

Myrna van Lunteren commented on DERBY-3604:
-------------------------------------------

Has this ever been seen again?

> Hang in .suites.All on 10.4 trunk ('Found one Java-level deadlock')
> -------------------------------------------------------------------
>
>                 Key: DERBY-3604
>                 URL: https://issues.apache.org/jira/browse/DERBY-3604
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.4.1.3
>         Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc.
> java version "1.6.0_01"
> Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
> Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode)
> SVN rev.: 645706
>            Reporter: Ole Solberg
>
> Seen on svn r645706.
> From http://dbtg.thresher.com/derby/test/tinderbox_10.4_16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/645706-org.apache.derbyTesting.functionTests.suites.All_diff.txt
:
> Found one Java-level deadlock:
> =============================
> "Finalizer":
>   waiting to lock monitor 0x080f372c (object 0xe4fee898, a org.apache.derby.impl.store.raw.data.StoredPage),
>   which is held by "main"
> "main":
>   waiting to lock monitor 0x080f3790 (object 0xe50a2810, a org.apache.derby.impl.store.raw.data.BaseContainerHandle),
>   which is held by "Finalizer"

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message