Temporarily hardcoding the port value in this test to the same value as TestConfiguration.DEFAULT_PORT, I was able to run all of suites.All successfully, so fixing this would allow running the suite with a different default port.
That does not mean that no server is started with port 1527 during the run of suite.All, however: DerbyNetNewServer run from NetHarnessJavaTest does not specify port when it starts a server, so this defaults to 1527 as well. By blocking 1527, I found no other instances of suite.All tests insisting on using it, so it seems the only two "culprits" right now are TestProto.java and DerbyNetNewServer.java. The singularity here would be a test, testing that the default actually being 1527, of course. The suite might skip such a test, were it to be made, in the case that TestConfiguration.port were set to a value other than 1527. Dag
