Can we switch the port used by PiTest

[caligarisdesk]

I noticed that PIT uses port 8092. Unfortunately, when running couchbase through vbox, pitest does not always detect that port 8092 is in use. As a result, pitest hangs.

http://www.speedguide.net/port.php?port=8092

pitest/pitest/src/main/java/org/pitest/util/SocketFinder.java

Line 25 in d4db566

private static final int MIN_PORT_NUMBER = 8091;

I didn't see that one could change the default port used. Can we add this as a parameter?

[caligarisdesk]

I'm not that familiar with socket libraries, but according to the SO below, should we also check DatagramSocket?

http://stackoverflow.com/questions/434718/sockets-discover-port-availability-using-java

[hcoles]

I think it might be possible to replace the whole thing with new ServerSocket(0).

This would change to port range to something outside of pitest's control so it can't be parameterised, but should push the responsibility for finding an ephemeral port to the JDK.

[hcoles]

@caligarisdesk I've published a 1.1.8 snapshot, can you let me know if it resolves the issue.

[caligarisdesk]

Cool, thanks! I'm having trouble pulling down a snapshot build, but as long as the port used keeps changing, it should work well for my configuration.

[hcoles]

@caligarisdesk 1.1.8 has now been released with this change. Can you report back if it has/hasn't resolved the issue.

[caligarisdesk]

Thanks for the release! Just brought 1.1.8 via the gradle plug-in with the same vagrant/couchbase condition as before. Pitest runs and completes successfully.