From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4462 invoked by alias); 1 Feb 2003 04:00:59 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 4455 invoked from network); 1 Feb 2003 04:00:58 -0000 Received: from unknown (HELO ms-smtp-02.southeast.rr.com) (24.93.67.83) by 172.16.49.205 with SMTP; 1 Feb 2003 04:00:58 -0000 Received: from mail4.nc.rr.com (fe4 [24.93.67.51]) by ms-smtp-02.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h113xno5022518; Fri, 31 Jan 2003 22:59:49 -0500 (EST) Received: from lyta.haphazard.org ([24.74.164.113]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Fri, 31 Jan 2003 23:02:02 -0500 Received: from lyta.haphazard.org (localhost.localdomain [127.0.0.1]) by lyta.haphazard.org (8.12.5/8.12.5) with ESMTP id h1140uGM022061; Fri, 31 Jan 2003 23:00:57 -0500 Received: (from cbj@localhost) by lyta.haphazard.org (8.12.5/8.12.5/Submit) id h1140uVB022057; Fri, 31 Jan 2003 23:00:56 -0500 X-Authentication-Warning: lyta.haphazard.org: cbj set sender to cbj@gnu.org using -f To: "Steve Murry" Cc: Subject: Re: Problems with port 30000 in .net.ServerSocketTest test_params testcase References: From: Brian Jones Date: Sat, 01 Feb 2003 04:00:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q1/txt/msg00014.txt.bz2 "Steve Murry" writes: > Many of the .net testcases use hard-coded port numbers when testing > the Socket and ServerSocket classes. Most of these port numbers > have not caused us any problems, with the exception of 30000. On > Compaq systems this is the port of an AFS management server, and > therefore any use of port 30000 causes the testcase to fail. The > first test_params() testcase in .net.ServerSocketTest creates a > ServerSocket bound to port 30000, which is then used to test various > ServerSocket methods. Would it be possible to alter this test so > that it either uses a different hard-coded port or specifies port 0, > which will allow the system to assign it a free port? With the > latter approach, the getLocalPort method will retrieve the port > number that was chosen. > > > Thanks, > Steve Murry > SAS Institute > Steve, we can change the port but this brings up the point it would be nice to have a way of specifying things like this outside of the testcase so it can be changed when needed. -- Brian Jones