db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5530) SQLChar.getCollationKey NPE in index-stat-thread
Date Thu, 02 Feb 2012 10:47:54 GMT

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

Kristian Waagan commented on DERBY-5530:

I'm unable to reproduce this (modified the istat test to run with a collated database).
Can you confirm that this is still a problem for you, and/or provide some more detail?
For instance:
 o JVM vendor/version
 o relevant part of the database schema, i.e. column types and indexes/constraints
 o istat lines from derby.log with derby.storage.indexStats.log=true and derby.storage.indexStats.debug.trace=true
(grep for "{istat}")
    Note: If the lines you included in the report are the only ones, ignore this.

I tried to reproduce on Solaris 11 with 1.6.0_26-b03 and 1.7.0_02-b13.
> SQLChar.getCollationKey NPE in index-stat-thread
> ------------------------------------------------
>                 Key: DERBY-5530
>                 URL: https://issues.apache.org/jira/browse/DERBY-5530
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>         Environment: Windows 7 - NetBeans 6.9.1
>            Reporter: Jean-Yves LINET
> With this JDBC connection url is : jdbc:derby:directory:db_name;territory=fr_FR;collation=TERRITORY_BASED:PRIMARY;create=true
> I get a NullPointerException in index-stat-thread
> Sun Dec 11 19:33:11 CET 2011 Thread[pool-3-thread-1,5,main] {istat} "PROXIFLEX"."IDAXX_RES":
update scheduled, reason=[no stats, row-estimate=375] (queueSize=1)
> Sun Dec 11 19:33:11 CET 2011 Thread[index-stat-thread,5,main] {istat,trace@26130360}
worker thread started (xid=12049) [q/p/s=1/0/1,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]
> Sun Dec 11 19:33:11 CET 2011 Thread[index-stat-thread,5,main] {istat,trace@26130360}
    processing "PROXIFLEX"."IDAXX_RES" 
> Sun Dec 11 19:33:11 CET 2011 Thread[index-stat-thread,5,main] {istat} runtime exception
during normal operation
> java.lang.NullPointerException
> 	at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown Source)
> 	at org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare(Unknown Source)
> 	at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare(Unknown Source)
> 	at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl$KeyComparator.compareWithPrevKey(Unknown
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.updateIndexStatsMinion(Unknown
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.generateStatistics(Unknown
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.processingLoop(Unknown
> 	at org.apache.derby.impl.services.daemon.IndexStatisticsDaemonImpl.run(Unknown Source)
> 	at java.lang.Thread.run(Thread.java:662)
> Sun Dec 11 19:33:11 CET 2011 Thread[index-stat-thread,5,main] {istat,trace@26130360}
worker thread exit [q/p/s=0/0/1,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]
> If I remove territory and collation parameters I don't have the exception.
> In case you want to disable automatic statistics, set derby property : derby.storage.indexStats.auto
to false.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message