[
https://issues.apache.org/jira/browse/DERBY-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558116#action_12558116
]
Mamta A. Satoor commented on DERBY-3302:
----------------------------------------
Committed a test case for this jira entry into trunk with revision 611295. the
commit comments were as follows
Adding a test case for DERBY-3302. There are two sub-test case classes involved
here, col_rec1.java and col_rec2.java
The purpose of col_rec1 test and col_rec2 test is to create a territory based
database and create some objects with collation sensitive character types.
Then, make the database crash so that during the recovery, store engine has to
do collation related operations. Those collation related operations are going
to require that we use correct Collator object. DERBY-3302 demonstrated a npe
during this operation because Derby was relying on database context to get the
correct Collator object. But database context is not available at this point in
the recovery. With the fix for DERBY-3302, the Collator object will now be
obtained from collation sensitive datatypes itself rather than looking at
database context which is not available at this point in recovery.
col_rec1 class will do the steps of create a territory based database and
create some objects with collation sensitive character types. Then, make the
database crash. col_rec2 class will do the part of rebooting the crashed db
which will require store to go through 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
> Fix For: 10.4.0.0
>
> 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.
