Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 14 Feb 2011 17:31:57 +0000 (UTC)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <729917552.15227.1297704717388.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1753687909.12114.1297471564002.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Resolved: (DERBY-5031) Exception in thread
 "index-stat-thread" java.lang.NullPointerException while calling
 ControlRow.getControlRowForPage(Unknown Source)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali resolved DERBY-5031.
-----------------------------------

    Resolution: Duplicate

> Exception in thread "index-stat-thread" java.lang.NullPointerException while calling ControlRow.getControlRowForPage(Unknown Source)
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5031
>                 URL: https://issues.apache.org/jira/browse/DERBY-5031
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.8.0.0
>         Environment: Sun Microsystems Inc.
> 1.6.0_181069888
> 2011-02-11 18:00:25 MET
>            Reporter: Mike Matrigali
>            Assignee: Mike Matrigali
>
> Nightly tests failed across many platforms with a number of failures.  I noticed this stack from the background
> istats threa hanging out at the end
> of the output file in a some of the cases.  I don't know if this stack caused the errors or not.  It may just be a bad
> error handling on shutdown.  It would be good to understand why it is printed when/where it is.  
> FAILURES!!!
> Tests run: 13369,  Failures: 3,  Errors: 1
> ------------------------------
> Exception in thread "index-stat-thread" java.lang.NullPointerException
> 	at org.apache.derby.impl.store.access.btree.ControlRow.getControlRowForPage(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.ControlRow.get(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.ControlRow.get(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.BTreeScan.reposition(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.BTreeForwardScan.fetchRows(Unknown Source)
> 	at org.apache.derby.impl.store.access.btree.BTreeScan.fetchNextGroup(Unknown Source)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl$KeyComparator.fetchRows(Unknown Source)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.updateIndexStatsMinion(Unknown Source)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.generateStatistics(Unknown Source)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.run(Unknown Source)
> 	at java.lang.Thread.run(Thread.java:619)
> Here are some links from sun nightly tests runs showing this error, it happened in a lot of the runs but not all the ones I looked at.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/lin/1069888-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1069888-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sol/1069888-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sol32/1069888-suitesAll_diff.txt

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