[ 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
