Hi Roger,
Thanks for the review. That permission is not actually required for the
test. But, it did make me look closer at it, and I realised that permission
checking of the request URI port number was not being tested. So, that
led me
down a couple of rat holes which is why I haven't replied t
Hi Michael,
Looks good, Roger
p.s. btw, the webrev diffs for 'Wdiffs' don't show anything.
On 5/4/2016 12:06 PM, Michael McMahon wrote:
Hi Roger,
Thanks for the review. That permission is not actually required for the
test. But, it did make me look closer at it, and I realised that
permissi
Michael,
getFreePort follows a failed pattern. There is no guarantee that the port will
be “free” when you actually require it. It will only reduce the likelihood of
failure. Is there any way that the actual tests needing the port can
create it themselves ( i understand that this will be mor
Hi Chris,
The problem is that the port number needs to be allocated outside the
test VM
because it needs to be specified as a system property given to the test VM.
This system property is then evaluated in the policy file to give permission
to that port.
I can't think of an easy way to close t
I've just updated the webrev at
http://cr.openjdk.java.net/~michaelm/8155928/webrev.3
to retry the tests in the unlikely event of a BindException
- Michael
On 04/05/16 19:12, Chris Hegarty wrote:
Michael,
getFreePort follows a failed pattern. There is no guarantee that the port will
be “free
* I see that there is an issue for autoponging. May be this falls under it.
The default impl of onPing() doesn't send PONG for *every* received PING.
Since it is against the protocol semantics, it forces all applications to
override the default onPing() impl. Is that right ?
It seems to me that th
