You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/14 19:30:21 UTC

[jira] [Closed] (DERBY-5085) After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true

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

Rick Hillegas closed DERBY-5085.
--------------------------------

    
> 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.1.2
>            Reporter: Rick Hillegas
>            Assignee: Lily Wei
>              Labels: derby_backport_reject_10_5
>             Fix For: 10.8.1.2
>
>         Attachments: DERBY-5085_1.diff, 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira