* Problems with port 30000 in .net.ServerSocketTest test_params testcase
@ 2003-01-30 20:11 Steve Murry
2003-02-01 4:00 ` Brian Jones
0 siblings, 1 reply; 2+ messages in thread
From: Steve Murry @ 2003-01-30 20:11 UTC (permalink / raw)
To: mauve-discuss
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problems with port 30000 in .net.ServerSocketTest test_params testcase
2003-01-30 20:11 Problems with port 30000 in .net.ServerSocketTest test_params testcase Steve Murry
@ 2003-02-01 4:00 ` Brian Jones
0 siblings, 0 replies; 2+ messages in thread
From: Brian Jones @ 2003-02-01 4:00 UTC (permalink / raw)
To: Steve Murry; +Cc: mauve-discuss
"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>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-02-01 4:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-30 20:11 Problems with port 30000 in .net.ServerSocketTest test_params testcase Steve Murry
2003-02-01 4:00 ` Brian Jones
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).