Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 2 Mar 2011 17:25:37 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2100447664.8258.1299086737249.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <104512757.8233.1299086256911.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-5085) After specifying deregister=false on
 the engine shutdown URL, Derby forgets that the default behavior is
 deregister=true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas updated DERBY-5085:
---------------------------------

    Labels: derby_triage10_8  (was: )

> After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5085
>                 URL: https://issues.apache.org/jira/browse/DERBY-5085
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.8.0.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_8
>         Attachments: y.java
>
>
> If you shutdown the engine specifying deregister=false, then get a new connection, then shutdown the engine again without specifying any value for the deregister attribute, Derby acts as though you specified deregister=false again. I will attach a test program which shows this problem.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira