From: Brian Jones <cbj@gnu.org>
To: "Steve Murry" <Steve.Murry@sas.com>
Cc: <mauve-discuss@sources.redhat.com>
Subject: Re: Problems with port 30000 in .net.ServerSocketTest test_params testcase
Date: Sat, 01 Feb 2003 04:00:00 -0000 [thread overview]
Message-ID: <m3y9503b0n.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <F2E670D5036BE14E89473A3FAEDE6ACE400C41@merc18.na.sas.com>
"Steve Murry" <Steve.Murry@sas.com> 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 <cbj@gnu.org>
prev parent reply other threads:[~2003-02-01 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 20:11 Steve Murry
2003-02-01 4:00 ` Brian Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y9503b0n.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=Steve.Murry@sas.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).