[
https://issues.apache.org/jira/browse/DERBY-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557721#action_12557721
]
Mamta A. Satoor commented on DERBY-3302:
----------------------------------------
Commited a fix for this into trunk using revision . I will work on merging this
into 10.3 codeline and writing a test case. The tests ran fine on my Windows XP
machine with Sun jdk1.4 The commit comments are as follows
DERBY-3302 The user was running into null pointer exception at the time of
database recovery
because Derby was trying to get the Collator object through database context.
But the
Collator object is already available in the territory sensitive character
classes and we
do not have to go to database context to get it. I changed the code to use that
collator
object rather than look into database context. The reason for null pointer
exception was
that database context was not loaded yet during database recovery.
> NullPointerException during recovery of database with territory-based
> collation
> -------------------------------------------------------------------------------
>
> Key: DERBY-3302
> URL: https://issues.apache.org/jira/browse/DERBY-3302
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Mamta A. Satoor
> Priority: Critical
> Attachments: npe.sql
>
>
> When logical undo is performed on a database with territory-based collation,
> you may get a NullPointerException in SQLChar.getCollationKey() because
> SQLChar.getLocaleFinder() returns null.
> This bug was reported on derby-user:
> http://thread.gmane.org/gmane.comp.apache.db.derby.user/8253
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
