Return-Path: 
 <derby-commits-return-17509-apmail-db-derby-commits-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-commits-archive@www.apache.org
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 119D610131
	for <apmail-db-derby-commits-archive@www.apache.org>;
 Tue, 10 Sep 2013 19:47:13 +0000 (UTC)
Received: (qmail 36840 invoked by uid 500); 10 Sep 2013 19:47:12 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 36785 invoked by uid 500); 10 Sep 2013 19:47:10 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-commits-help@db.apache.org>
list-unsubscribe: <mailto:derby-commits-unsubscribe@db.apache.org>
List-Post: <mailto:derby-commits@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
List-Id: <derby-commits.db.apache.org>
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 36763 invoked by uid 99); 10 Sep 2013 19:47:06 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Sep 2013 19:47:06 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Sep 2013 19:47:04 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id 22A6F23888A6;
	Tue, 10 Sep 2013 19:46:43 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1521608 -
 /db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita
Date: Tue, 10 Sep 2013 19:46:43 -0000
To: derby-commits@db.apache.org
From: chaase3@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20130910194643.22A6F23888A6@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: chaase3
Date: Tue Sep 10 19:46:42 2013
New Revision: 1521608

URL: http://svn.apache.org/r1521608
Log:
DERBY-6165  The shutdown documentation should mention that a shutdown attempt could fail if login timeouts are enabled.  

Added paragraph to a Developer's Guide topic.

Patch: DERBY-6165.diff

Modified:
    db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita

Modified: db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita?rev=1521608&r1=1521607&r2=1521608&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita Tue Sep 10 19:46:42 2013
@@ -64,6 +64,14 @@ can shut down the database.
 <codeblock><b>// shutting down an authenticated database as database owner</b>
 DriverManager.getConnection(
     "jdbc:derby:securesample;user=joeowner;password=secret;shutdown=true");</codeblock>
+<p>If you previously called the <i>java.sql.DriverManager.setLoginTimeout</i>
+method to enable a login timeout, a shutdown of
+<ph conref="../conrefs.dita#prod/productshortname"></ph> or of an individual
+database can fail under circumstances like the following:</p>
+<ul>
+<li>Network problems which slow down LDAP authentication</li>
+<li>Heavily loaded databases which take a long time time to quiesce</li>
+</ul>
 <p>
 <note type="attention"> 
 It is good practice to close existing connections before shutting down