db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [Db-derby Wiki] Update of "DerbyJUnitTesting" by TiagoEspinha
Date Fri, 26 Jun 2009 22:26:34 GMT
Tiago Espinha <tiago@espinhas.net> writes:

> Interesting. I did address replication in
> replicationTests/ReplicationRun.java and all the ports there were taken care
> of. I'm not sure about this 4851 port. This port isn't mentioned anywhere in
> the tests and it might be that the ReplicationRun was actually overriding
> this port for some reason.

Right. If an explicit port is used in all the replication tests, we
should be ok :) Thanks for fixing this.

Thanks,
Dag
>
> -----------------8<---------------
> slaveServerPort = 4527;
> util.DEBUG("slaveServerPort: " + slaveServerPort);
> slaveReplPort = 8888;
> ------------------8<---------------
>
> This is how the ReplicationRun was defining the ports. Now all the
> alternative, replication and JMX ports are offsets from the basePort
> property (or from 1527 if a property isn't set).

Mime
View raw message