I got rid of the new finder class in favor of the existing one. If I reuse the one from Mina it does not work due to port range issues.
Gary Gary <div>-------- Original message --------</div><div>From: Matt Sicker <boa...@gmail.com> </div><div>Date:06/25/2014 11:02 (GMT-05:00) </div><div>To: Log4J Developers List <log4j-dev@logging.apache.org> </div><div>Subject: Re: Finding free ports </div><div> </div>I think AvailablePortFinder was a class I copied from Camel. On 24 June 2014 23:24, Gary Gregory <garydgreg...@gmail.com> wrote: We have two ways of finding free socket ports: - org.apache.logging.log4j.test.AvailablePortFinder has been around for a while, and - org.apache.logging.log4j.core.net.FreePortFinder which is a new class I refactored out of a bunch of duplicate code in the Flume tests. We need to pick on way of doing this. FreePortFinder gets my vote because it is simpler. Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- Matt Sicker <boa...@gmail.com>
