db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <kristian.waa...@oracle.com>
Subject Re: regression test regressed
Date Wed, 14 Jul 2010 07:44:40 GMT
On 14.07.10 09:24, Tiago Espinha wrote:
> It means that at some point in time during a suites.All run, each of the ports
> in the range [basePort, basePort+10] will be in use.

Just a minor detail, but I think it means each of the ports *may* be in 
use at some point.
For instance, not all runs will use the JMX port. If you run an embedded 
test only, no ports will be actually used.


> They won't all be in use at
> the same time but we assume that any combination of them might be and as such,
> we know to keep away from that range for other parallel test runs. We also know
> that it'd be a mistake to set a base port of, for example, 70 if you have a web
> server running on that machine, as it eventually will go up to port 80 and it
> will fail because it can't bind on it.
> Tiago
> ----- Original Message ----
> From: Knut Anders Hatlen<knut.hatlen@oracle.com>
> To: derby-dev@db.apache.org
> Sent: Tue, 13 July, 2010 23:11:42
> Subject: Re: regression test regressed
> On 07/13/10 10:33 PM, Tiago Espinha wrote:
>> I think ideally we'd keep the max number of ports on a tight fit to what is
>> actually needed, that's why I left them at 10. This way if new ports are
>> required along the way, whoever makes the changes gets alerted that they need
>> to
>> increase this constant.
> What does the limit of 10 ports mean, exactly? Does it mean that there
> could be a maximum of 10 ports in use at the same time? Or does it mean
> that a maximum of 10 tests can use an alternative port?
> Thanks,

View raw message