[
https://issues.apache.org/jira/browse/DERBY-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543704
]
Dag H. Wanvik commented on DERBY-3215:
--------------------------------------
I should mention that the wrong usage of FILE_WRITE_PAGE_EXCEPTION occurs in
one more
instance in the same method (except for the one susceptible to the empty
pointer). The patch
corrects both instances. There are no occurences in other classes.
> Potential NullPointerException in CachedPage class
> --------------------------------------------------
>
> Key: DERBY-3215
> URL: https://issues.apache.org/jira/browse/DERBY-3215
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.3.1.4
> Environment: Windows XP
> Reporter: Jason Valentine
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: DERBY-3215.diff
>
>
> There's a potential for a NullPointerException to be thrown in the in the
> org.apache.derby.impl.store.raw.data.CachedPage class. In the writePage()
> method, there's a test of the myContainer reference to ensure it's not null
> (line 771), however in the else block, myContainer is dereferenced (line
> 836), where a NullPointerException is guaranteed to be thrown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
