From derby-user-return-14932-apmail-db-derby-user-archive=db.apache.org@db.apache.org Wed Feb 27 03:41:14 2013 Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7753DF13 for ; Wed, 27 Feb 2013 03:41:14 +0000 (UTC) Received: (qmail 96105 invoked by uid 500); 27 Feb 2013 03:41:14 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 95627 invoked by uid 500); 27 Feb 2013 03:41:10 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 95591 invoked by uid 99); 27 Feb 2013 03:41:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 03:41:09 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dag.wanvik@oracle.com designates 141.146.126.69 as permitted sender) Received: from [141.146.126.69] (HELO aserp1040.oracle.com) (141.146.126.69) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 03:40:59 +0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r1R3ec0h017015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 27 Feb 2013 03:40:38 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r1R3ebIO015246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Feb 2013 03:40:37 GMT Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r1R3ebsL001430 for ; Tue, 26 Feb 2013 21:40:37 -0600 Received: from [10.159.173.55] (/10.159.173.55) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 26 Feb 2013 19:40:37 -0800 Message-ID: <512D8034.2020403@oracle.com> Date: Wed, 27 Feb 2013 13:40:36 +1000 From: Dag Wanvik Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Derby Discussion Subject: Re: Recommended sequences of shutdown of Derby Network Server and Derby Engine References: <1361888967.42892.YahooMailNeo@web162803.mail.bf1.yahoo.com> In-Reply-To: <1361888967.42892.YahooMailNeo@web162803.mail.bf1.yahoo.com> Content-Type: multipart/alternative; boundary="------------040501070100060508090708" X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------040501070100060508090708 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 27.02.2013 00:29, Oskar Zinger wrote: > What's the recommended sequence of shutdown of Derby... if for example > I have Derby Network Server and Derby Engine running. What should be > shutdown first? > > Currently, I shutdown Network Server and then the Engine, the reason > is so that Derby does not get rebooted by someone else making a call. Sounds like a good approach to me. The network server is "really" just an application using the Derby engine via the embedded JDBC driver. Stopping the server before the database engine is therefore fine. Thanks, Dag > > Thanks, > Oskar --------------040501070100060508090708 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 27.02.2013 00:29, Oskar Zinger wrote:
What's the recommended sequence of shutdown of Derby... if for example I have Derby Network Server and Derby Engine running. What should be shutdown first?

Currently, I shutdown Network Server and then the Engine, the reason is so that Derby does not get rebooted by someone else making a call.

Sounds like a good approach to me. The network server is "really" just an application using the Derby engine via the embedded JDBC driver.
Stopping the server before the database engine is therefore fine.

Thanks,
Dag


Thanks,
Oskar

--------------040501070100060508090708--