Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 51528 invoked from network); 29 Jun 2006 14:53:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Jun 2006 14:53:10 -0000 Received: (qmail 75965 invoked by uid 500); 29 Jun 2006 14:53:10 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 75760 invoked by uid 500); 29 Jun 2006 14:53:09 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 75745 invoked by uid 99); 29 Jun 2006 14:53:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 07:53:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 07:53:08 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 17DD2410123 for ; Thu, 29 Jun 2006 14:51:31 +0000 (GMT) Message-ID: <16904871.1151592691095.JavaMail.jira@brutus> Date: Thu, 29 Jun 2006 14:51:31 +0000 (GMT+00:00) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1465) NetworkServerControl.start() should throw an exception and not just print exceptions if the server fails to start In-Reply-To: <20510964.1151587050017.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1465?page=comments#action_12418481 ] John H. Embretsen commented on DERBY-1465: ------------------------------------------ The relationship between the Network Server API and the derby.drda.startNetworkServer property (and its related functionality) is indeed puzzling. See my comment to DERBY-1326 (June 16th), particularly observation b), for another example: http://issues.apache.org/jira/browse/DERBY-1326#action_12416494 > NetworkServerControl.start() should throw an exception and not just print exceptions if the server fails to start > -------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1465 > URL: http://issues.apache.org/jira/browse/DERBY-1465 > Project: Derby > Type: Bug > Components: Network Server > Versions: 10.1.2.1 > Reporter: Kathey Marsden > Priority: Minor > > NetworkServerControl.start() will not throw an exception if another server is already running on the same port. I am not sure but think perhaps this was changed at one point to accomodate the derby.drda.startNetworkServer property so that the embedded server could continue to boot even if the network server failed to start, but I think this is wrong for normal usage. > http://www.nabble.com/Questions-about-Network-Server-API-Behavior-p5055814.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira