db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6833) NPE in IndexRowGenerator.getExecutionFactory()
Date Sat, 12 Sep 2015 03:20:45 GMT

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

Mike Matrigali commented on DERBY-6833:
---------------------------------------

is it likely or not that your system may have been executing something that would have been
creating an index "around" the time of the error?
A number of ddl options might do this:
create index
add constraint
offline compress
some versions of add and drop column
...

> NPE in IndexRowGenerator.getExecutionFactory()
> ----------------------------------------------
>
>                 Key: DERBY-6833
>                 URL: https://issues.apache.org/jira/browse/DERBY-6833
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.11.1.1
>         Environment: Tue Sep 08 19:39:37 EDT 2015:
> Booting Derby version The Apache Software Foundation - Apache Derby - 10.11.1.1 - (1616546):
instance a816c00e-014f-af54-3c5f-0000350a3da0 
> on database directory /mnt/raid0/jenkins/grid/main/deployment/integration-tests/build/grid/var/apps/archive/database/jyrusNodeDb
with class loader sun.misc.Launcher$AppClassLoader@7852e922 
> Loaded from file:/mnt/raid0/jenkins/grid/main/deployment/integration-tests/build/grid/lib/derby-10.11.1.1.jar
> java.vendor=Oracle Corporation
> java.runtime.version=1.8.0_45-b14
> user.dir=/mnt/raid0/jenkins/grid/main/deployment/integration-tests/build/grid/bin
> os.name=Linux
> os.arch=amd64
> os.version=2.6.32-431.29.2.el6.x86_64
> derby.system.home=null
> Database Class Loader started - derby.database.classpath=''
>            Reporter: Edward Howe
>            Priority: Critical
>
> Derby crashed with the following stack trace while running our application's integration
tests.  This is the first time I've seen this, and cannot reproduce it.  It happened during
our application's startup.  The embedded database had been opened by this point, and some
initial queries had been executed.  
> java.lang.NullPointerException: null
> 	at org.apache.derby.iapi.sql.dictionary.IndexRowGenerator.getExecutionFactory(Unknown
Source) ~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.iapi.sql.dictionary.IndexRowGenerator.getIndexRowTemplate(Unknown
Source) ~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.iapi.sql.dictionary.IndexRowGenerator.getNullIndexRow(Unknown Source)
~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.updateIndexStatsMinion(Unknown
Source) ~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.generateStatistics(Unknown
Source) ~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.processingLoop(Unknown
Source) ~[derby-10.11.1.1.jar:na]
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.run(Unknown Source)
~[derby-10.11.1.1.jar:na]
> 	at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_45]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message