Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: 32.97.182.144 is neither permitted nor
 denied by domain of Stan.Bradbury@gmail.com)
Message-ID: <42DE9E49.3020201@gmail.com>
Date: Wed, 20 Jul 2005 11:56:09 -0700
From: Stanley Bradbury <Stan.Bradbury@gmail.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Derby hanging on port conflict
References: <103b222c05071114204fc1ce63@mail.gmail.com>
In-Reply-To: <103b222c05071114204fc1ce63@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Simon -
I was not able to hang the Network Server by issuing  
'...NetworkServerControl start' multiple times - I was using the default 
host and port.  Can you describe how this occurs in your environment or 
provide demonstration code or scrip?.  Please also include the 
information from SYSINFO so I know what version you are using.

Thanks,  Stan

Simon wrote:

> Hi all,
>
> I notice if I accidently start 2 instances of Derby Network Server on 
> the same port, not only does the 2nd instance get the binding to the 
> port rejected but the 1st instance hangs as well.   This seems to 
> happen on both linux and windows.
>
> Anyone know if there is a reason this is happening/way to prevent 
> it?   Derby-devs - is this worth logging as a bug?
>
> (context is that we want to run lots of Derby servers on the same 
> box.   right now, even when separated as different users accidently 
> starting a derby server on a conflicting port kills the other instance 
> - this is bad - it means a non-privileged user can take down a derby 
> instance owned by someone else... ).
>
> Thanks for any help or info!
>
> Cheers,
>
> Simon.