Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 26 Aug 2016 01:09:20 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12998867.1471867830000.416199.1472173760464@Atlassian.JIRA>
In-Reply-To: <JIRA.12998867.1471867830000@Atlassian.JIRA>
References: <JIRA.12998867.1471867830000@Atlassian.JIRA> <JIRA.12998867.1471867830070@arcas>
Subject: [jira] [Commented] (DERBY-6908) CLONE - Incorrect error message in
 ij for disconnect with no active connections
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 26 Aug 2016 01:09:22 -0000


    [ https://issues.apache.org/jira/browse/DERBY-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438239#comment-15438239 ] 

Bryan Pendleton commented on DERBY-6908:
----------------------------------------

I think maybe this CLONE issue was created accidentally? I don't think we
typically create clone issues in the Derby JIRA?

> CLONE - Incorrect error message in ij for disconnect with no active connections
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-6908
>                 URL: https://issues.apache.org/jira/browse/DERBY-6908
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.2.2.0
>            Reporter: M.A.D.M Mallikarachchi
>            Priority: Minor
>              Labels: derby_triage10_5_2
>
> Using ij, before connecting to the database, when the disconnect command is issued, the error message which is printed is:IJ ERROR: Unable to establish connection
> bash-3.00# ij
> ij version 10.4
> ij> disconnect;
> IJ ERROR: Unable to establish connection
> The error message should be changed to "No connection available" for a better understanding.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)