Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C3C4D10484 for ; Fri, 23 Aug 2013 15:31:55 +0000 (UTC) Received: (qmail 11623 invoked by uid 500); 23 Aug 2013 15:31:53 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 11554 invoked by uid 500); 23 Aug 2013 15:31:52 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 11540 invoked by uid 99); 23 Aug 2013 15:31:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Aug 2013 15:31:52 +0000 Date: Fri, 23 Aug 2013 15:31:52 +0000 (UTC) From: "stack (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-9319) Apply 'HBASE-7685 Closing socket connection can't be removed from SecureClient' to trunk 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/HBASE-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-9319. -------------------------- Resolution: Fixed Fix Version/s: 0.96.0 0.98.0 Assignee: stack Committed to trunk and to 0.95 branch. > Apply 'HBASE-7685 Closing socket connection can't be removed from SecureClient' to trunk > ---------------------------------------------------------------------------------------- > > Key: HBASE-9319 > URL: https://issues.apache.org/jira/browse/HBASE-9319 > Project: HBase > Issue Type: Bug > Reporter: stack > Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9319.txt > > > [~liuxiong] notes we failed to apply hbase-7685 to trunk (over in HBASE-7685). This issue fixes this oversight. -- 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