[
https://issues.apache.org/jira/browse/DERBY-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845383#comment-13845383
]
Dag H. Wanvik edited comment on DERBY-6354 at 12/11/13 1:36 PM:
----------------------------------------------------------------
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 code:
{noformat}
if (SanityManager.DEBUG)
{
SanityManager.ASSERT(isLatched());
SanityManager.ASSERT(
!isLast(), "next alloc page not present for last alloc page");
}
return nextAllocPageNumber;
{noformat}
But we didn't see this assert, so....
Not sure how to interpret this...but maybe it's just a follow-on problem caused
by the first error.
was (Author: dagw):
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 code:
{noformat}
if (SanityManager.DEBUG)
{
SanityManager.ASSERT(isLatched());
SanityManager.ASSERT(
!isLast(), "next alloc page not present for last alloc page");
}
return nextAllocPageNumber;
{noformat}
Not sure how to interpret this...but maybe it's just a follow-on problem caused
by the first error.
> 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: 10.11.0.0
> 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
(v6.1.4#6159)
