Hi,
please review the following patch. It generally coverts codes from
shell to plain java.
Bug:
https://bugs.openjdk.java.net/browse/JDK-8169115
Webrev:
http://cr.openjdk.java.net/~xiaofeya/8169115/webrev.00/
Thanks,
Felix
While the idea is good I think this will not “fly” because for windows winsock
is used in the JDK. Winsock does not use the same error constant as bsd sockets
API (with errno).
In windows we would need to expose “WSAGetLastError()” values and in
unix/linux/bsd “errno” values. Sure we could try t
Hi,
I would also support if IOException could be enriched to expose the native
error code. However, the user then would need to evaluate this code in a
platform specific manner. Maybe there could be some class/interface which would
help to translate platform specific error codes to common const
Felix,
1. I'm not sure that javaweb.sfbay.sun.com is the best domain name for
this test. Could we use different one (e.g. icann.org)
2. This test run JTREG -> Test VM -> Another VM. Could we optimize
process usage?
It might be better to create a jtreg "same vm" process that
1. launch another
