Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.10.1.1
-
None
-
Normal
Description
Database/engine shutdown can fail if a login timeout is enabled via DriverManager.setLoginTimeout(). This can happen, for example, for the following reasons:
A) Network problems which slow down LDAP authentication.
B) Heavily loaded databases which need a lot of time to quiesce.
We should document this fact in the "Shutting down Derby or an individual database" section of the Derby Developer's Guide. This issue was discussed on the following derby-dev email thread: http://apache-database.10148.n7.nabble.com/should-attempts-to-shut-down-the-database-timeout-if-they-exceed-DriverManager-setLoginTimeout-N-td128966.html