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


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

        

Reply via email to