accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1891) AccumuloSecurityException doesn't properly handle null error codes.
Date Thu, 14 Nov 2013 05:53:21 GMT

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

Sean Busbey updated ACCUMULO-1891:
----------------------------------

    Fix Version/s: 1.6.0
                   1.5.1
                   1.4.5
           Status: Patch Available  (was: Open)

Looks like this issue carries through to master. Fix is simple enough that I'm skipping a
review board for the patch.

> AccumuloSecurityException doesn't properly handle null error codes.
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-1891
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1891
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>         Attachments: ACCUMULO-1891.1.patch.txt
>
>
> As a part of fixing ACCUMULO-1878 I hit an error condition in examples.simple.isolation.InterferenceTest$Writer
where a security exception hits a path that doesn't properly handle a null coming out of thrift.
> {code}
> Caused by: java.lang.NullPointerException
>         at org.apache.accumulo.core.client.AccumuloSecurityException.getDefaultErrorMessage(AccumuloSecurityException.java:30)
>         at org.apache.accumulo.core.client.AccumuloSecurityException.<init>(AccumuloSecurityException.java:70)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchReaderIterator.doLookup(TabletServerBatchReaderIterator.java:579)
>         at org.apache.accumulo.core.client.impl.MetadataLocationObtainer.lookupTablets(MetadataLocationObtainer.java:150)
>         at org.apache.accumulo.core.client.impl.TabletLocatorImpl.processInvalidated(TabletLocatorImpl.java:591)
>         at org.apache.accumulo.core.client.impl.TabletLocatorImpl.binRanges(TabletLocatorImpl.java:272)
>         at org.apache.accumulo.core.client.impl.TabletLocatorImpl.processInvalidated(TabletLocatorImpl.java:584)
>         at org.apache.accumulo.core.client.impl.TabletLocatorImpl.binMutations(TabletLocatorImpl.java:126)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter$MutationWriter.binMutations(TabletServerBatchWriter.java:560)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter$MutationWriter.addMutations(TabletServerBatchWriter.java:600)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter.startProcessing(TabletServerBatchWriter.java:180)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter.addFailedMutations(TabletServerBatchWriter.java:471)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter.access$700(TabletServerBatchWriter.java:94)
>         at org.apache.accumulo.core.client.impl.TabletServerBatchWriter$FailedMutations.run(TabletServerBatchWriter.java:523)
> {code} 
> Looking at the code for AccumuloSecurityException, everything except for getDefaultErrorMessage
accounts for the error code being null.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message