Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCD90D6D3 for ; Tue, 5 Mar 2013 21:48:13 +0000 (UTC) Received: (qmail 75784 invoked by uid 500); 5 Mar 2013 21:48:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 75717 invoked by uid 500); 5 Mar 2013 21:48:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 75708 invoked by uid 99); 5 Mar 2013 21:48:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Mar 2013 21:48:13 +0000 Date: Tue, 5 Mar 2013 21:48:13 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-295) Client side metadata cache caches credentials MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Vines updated ACCUMULO-295: -------------------------------- Fix Version/s: 1.5.0 > Client side metadata cache caches credentials > --------------------------------------------- > > Key: ACCUMULO-295 > URL: https://issues.apache.org/jira/browse/ACCUMULO-295 > Project: Accumulo > Issue Type: Bug > Components: client > Affects Versions: 1.4.0, 1.3.5 > Reporter: Keith Turner > Assignee: John Vines > Fix For: 1.5.0 > > > Saw the following while running the random walk test. Not sure, but I think this is a bug with the test. I think it does not properly handle the bad credentials case. > {noformat} > 09 20:40:40,275 [randomwalk.Framework] ERROR: Error during random walk > java.lang.Exception: Error running node Security.xml > at org.apache.accumulo.server.test.randomwalk.Module.visit(Module.java:236) > at org.apache.accumulo.server.test.randomwalk.Framework.run(Framework.java:61) > at org.apache.accumulo.server.test.randomwalk.Framework.main(Framework.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.accumulo.start.Main$1.run(Main.java:89) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.Exception: Error running node security.TableOp > at org.apache.accumulo.server.test.randomwalk.Module.visit(Module.java:236) > at org.apache.accumulo.server.test.randomwalk.Module.visit(Module.java:234) > ... 8 more > Caused by: org.apache.accumulo.core.client.AccumuloException: Unexpected exception! > at org.apache.accumulo.server.test.randomwalk.security.TableOp.visit(TableOp.java:125) > at org.apache.accumulo.server.test.randomwalk.Module.visit(Module.java:234) > ... 9 more > Caused by: java.lang.RuntimeException: org.apache.accumulo.core.client.AccumuloSecurityException: Error BAD_CREDENTIALS - Username or Password is Invalid > at org.apache.accumulo.core.client.impl.ScannerIterator.hasNext(ScannerIterator.java:186) > at org.apache.accumulo.server.test.randomwalk.security.TableOp.visit(TableOp.java:90) > ... 10 more > Caused by: org.apache.accumulo.core.client.AccumuloSecurityException: Error BAD_CREDENTIALS - Username or Password is Invalid > at org.apache.accumulo.core.client.impl.TabletServerBatchReaderIterator.doLookup(TabletServerBatchReaderIterator.java:576) > at org.apache.accumulo.core.client.impl.MetadataLocationObtainer.lookupTablets(MetadataLocationObtainer.java:146) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl.processInvalidated(TabletLocatorImpl.java:580) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl._locateTablet(TabletLocatorImpl.java:524) > at org.apache.accumulo.core.client.impl.TabletLocator$1._locateTablet(TabletLocator.java:115) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl.locateTablet(TabletLocatorImpl.java:370) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl.lookupTabletLocation(TabletLocatorImpl.java:390) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl._locateTablet(TabletLocatorImpl.java:536) > at org.apache.accumulo.core.client.impl.TabletLocatorImpl.locateTablet(TabletLocatorImpl.java:370) > at org.apache.accumulo.core.client.impl.ThriftScanner.scan(ThriftScanner.java:245) > at org.apache.accumulo.core.client.impl.ScannerIterator$Reader.run(ScannerIterator.java:94) > at org.apache.accumulo.core.client.impl.ScannerIterator.hasNext(ScannerIterator.java:176) > ... 11 more > Caused by: ThriftSecurityException(user:xxx, code:BAD_CREDENTIALS) > at org.apache.accumulo.core.tabletserver.thrift.TabletClientService$startMultiScan_result.read(TabletClientService.java:7586) > at org.apache.accumulo.core.tabletserver.thrift.TabletClientService$Client.recv_startMultiScan(TabletClientService.java:306) > at org.apache.accumulo.core.tabletserver.thrift.TabletClientService$Client.startMultiScan(TabletClientService.java:274) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at cloudtrace.instrument.thrift.TraceWrap$2.invoke(TraceWrap.java:83) > at $Proxy4.startMultiScan(Unknown Source) > at org.apache.accumulo.core.client.impl.TabletServerBatchReaderIterator.doLookup(TabletServerBatchReaderIterator.java:539) > ... 22 more > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira