You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2008/08/08 13:39:44 UTC

[jira] Updated: (HADOOP-3506) Occasional NPE in Jets3tFileSystemStore

     [ https://issues.apache.org/jira/browse/HADOOP-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated HADOOP-3506:
------------------------------

    Attachment: hadoop-3506.patch

Patch with a fix for this issue.

> Occasional NPE in Jets3tFileSystemStore
> ---------------------------------------
>
>                 Key: HADOOP-3506
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3506
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.17.0
>            Reporter: Robert
>         Attachments: hadoop-3506.patch
>
>
> In extraordinary circumstances (eg. S3 outages), calling S3FileSystem functions will throw NullPointerExceptions when trying to read from the filesystem. I've traced this down to calls to Jets3tFileSystemStore.get().
> Both get() functions catch an S3ServiceException, and check its error code using a string comparison. However, the underlying libs3t library will sometimes produce an exception with a null error code string. This results in an NPE that propagates all the way to the S3FileSystem, and to the caller.
> To fix this, Jets3tFileSystemStore lines 196 and 212 should be changed from:
> bq.         if (e.getS3ErrorCode().equals("NoSuchKey")) {
> to:
> bq.         if ("NoSuchKey".equals(e.getS3ErrorCode())) {

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.