Updated webrev: http://cr.openjdk.java.net/~jboes/webrevs/8232513/webrev.01/
On 06/12/2019 17:05, Vyom Tewari26 wrote:
Your change looks OK but it will increase the worst case, running time
of test from (2500+1000)ms to (15000 + 1000)ms and this will definitely
decrease the probability of
Hi Julia,
Your change looks OK but it will increase the worst case, running time of test from (2500+1000)ms to (15000 + 1000)ms and this will definitely decrease the probability of intermittent failure but not 100% full proof.
Thanks,
Vyom
- Original message -From: Julia Boes
Hi Mark,
The test has a potential problem, that is the socket close can
cause the attempted send from server socket to client not to occur.
the sock.send() can result in the application data being copied into the
kernel and queued for sending. But the send may not take place
immediately.
From: net-dev on behalf of Daniel Fuchs
Sent: Wednesday 4 December 2019 16:10
To: Julia Boes ; OpenJDK Network Dev list
Subject: Re: RFR: 8232513: java/net/DatagramSocket/PortUnreachable.java still
fails intermittently with BindException
Hi Julia,
Looks good to me - but is
Hi Julia,
Looks good to me - but is:
31 * @library /test/lib
actually needed?
best regards,
-- daniel
On 04/12/2019 15:40, Julia Boes wrote:
Hi,
The test PortUnreachable closes a DatagramSocket and tries to rebind it
to the same port, this causes the test to fail rarely with a
Hi,
The test PortUnreachable closes a DatagramSocket and tries to rebind it
to the same port, this causes the test to fail rarely with a
BindException (I did 500 test runs and couldn't observe a failure). To
decrease the likelihood of this to happen, the fix increases the number
of bind
