db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@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
Date Wed, 02 Mar 2011 19:57:37 GMT

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

Lily Wei updated DERBY-5085:
----------------------------

    Attachment: DERBY-5085_1.diff

Thanks, Rick. Upload patch DERBY-5085_1.diff. With this patch, derby will keep the default
behavior deregister=true after shutdown derby with deregister=false.

> 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
>            Assignee: Lily Wei
>              Labels: derby_triage10_8
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message