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 "Kim Haase (JIRA)" <ji...@apache.org> on 2013/09/10 20:15:53 UTC
[jira] [Assigned] (DERBY-6165) The shutdown documentation should
mention that a shutdown attempt could fail if login timeouts are enabled.
[ https://issues.apache.org/jira/browse/DERBY-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-6165:
--------------------------------
Assignee: Kim Haase
> The shutdown documentation should mention that a shutdown attempt could fail if login timeouts are enabled.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6165
> URL: https://issues.apache.org/jira/browse/DERBY-6165
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> 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
--
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