db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DERBY-6165) The shutdown documentation should mention that a shutdown attempt could fail if login timeouts are enabled.
Date Tue, 10 Sep 2013 18:15:53 GMT

     [ 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

Mime
View raw message