db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6354) DatabaseMetaDataTest.testGetColumnsReadOnly fails with NPE when releasing page
Date Wed, 11 Dec 2013 13:34:07 GMT

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

Dag H. Wanvik commented on DERBY-6354:

Hi Knut; your right about the extra diagnostics; for some reason I thought I didn't see the
stack in the report.. in any case, it seems the -1 page number comes all the way from AllocationCache.java.
I am not that familiar with that code; is it possible it could ask for a page number -1 from
there? I see AllocPage uses -1 for INVALID_PAGE_NUMBER... I see allocPageNumber has this Sanity
if (SanityManager.DEBUG)
    !isLast(), "next alloc page not present for last alloc page");
return nextAllocPageNumber;
Not sure how to interpret this...

> DatabaseMetaDataTest.testGetColumnsReadOnly fails with NPE when releasing page
> ------------------------------------------------------------------------------
>                 Key: DERBY-6354
>                 URL: https://issues.apache.org/jira/browse/DERBY-6354
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Attachments: derby-6343-diag.diff, fail-solaris.zip, fail-windows.zip
> Seen twice in the nightly testing lately:
> http://download.java.net/javadesktop/derby/request_5581975/javadb-task-3729984.html
> http://download.java.net/javadesktop/derby/request_5581997/javadb-task-3730576.html
> Both failures happened with JDK 8-ea-b107 (Windows and Solaris).

This message was sent by Atlassian JIRA

View raw message