net-dev  

Messages by Thread

• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v18] Volkan Yazıcı
• RFR: 8344856: Remove calls to SecurityManager and doPrivileged in subclasses of URLConnection in the sun.net package after JEP 486 integration Volkan Yazıcı
  • Re: RFR: 8344856: Remove calls to SecurityManager and doPrivileged in subclasses of URLConnection in the sun.net package after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344856: Remove calls to SecurityManager and doPrivileged in subclasses of URLConnection in the sun.net package after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344856: Remove calls to SecurityManager and doPrivileged in subclasses of URLConnection in the sun.net package after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344856: Remove calls to SecurityManager and doPrivileged in subclasses of URLConnection in the sun.net package after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344856: Remove calls to SecurityManager and doPrivileged in sun.net.www.protocol.ftp.FtpURLConnection after JEP 486 integration [v2] duke
  • Integrated: 8344856: Remove calls to SecurityManager and doPrivileged in sun.net.www.protocol.ftp.FtpURLConnection after JEP 486 integration Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
• RFR: 8344184: Remove sun.net.ResourceManager after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344184: Remove sun.net.ResourceManager after JEP 486 integration Alan Bateman
  • Integrated: 8344184: Remove sun.net.ResourceManager after JEP 486 integration Daniel Fuchs
• RFR: Mark not subclassable classes final in java.base exported classes Eirik Bjørsnøs
  • Re: RFR: Mark not subclassable classes final in java.base exported classes Eirik Bjørsnøs
  • Re: RFR: Mark not subclassable classes final in java.base exported classes Jaikiran Pai
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Daniel Fuchs
• Re: RFR: 8338445: jdk.internal.loader.URLClassPath may leak JarFile instance when dealing with unexpected Class-Path entry in manifest [v2] Jaikiran Pai
• RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Aleksei Efimov
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Volkan Yazıcı
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Alan Bateman
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Aleksei Efimov
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration [v2] Aleksei Efimov
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration [v2] Alan Bateman
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration [v3] Aleksei Efimov
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration [v3] Jaikiran Pai
  • Re: RFR: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration [v3] Daniel Fuchs
  • Integrated: 8344220: Remove calls to SecurityManager and doPrivileged in java.net.InetAddress and sun.net.util.IPAddressUtil after JEP 486 integration Aleksei Efimov
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v15] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
• Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
• RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Alan Bateman
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v2] Alan Bateman
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v3] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v3] Alan Bateman
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v3] Eirik Bjørsnøs
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v3] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v4] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v4] Jaikiran Pai
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v4] Alan Bateman
  • Re: RFR: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs [v4] Jaikiran Pai
  • Integrated: 8344908: URLClassPath should not propagate IllegalArgumentException when finding resources in classpath URLs Jaikiran Pai
• RFR: 8344857: Remove calls to SecurityManager and doPrivileged in SocketExceptions and URLJarFile in the sun.net package after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344857: Remove calls to SecurityManager and doPrivileged in SocketExceptions and URLJarFile in the sun.net package after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344857: Remove calls to SecurityManager and doPrivileged in SocketExceptions and URLJarFile in the sun.net package after JEP 486 integration Michael McMahon
  • Re: RFR: 8344857: Remove calls to SecurityManager and doPrivileged in SocketExceptions and URLJarFile in the sun.net package after JEP 486 integration Jaikiran Pai
  • Integrated: 8344857: Remove calls to SecurityManager and doPrivileged in SocketExceptions and URLJarFile in the sun.net package after JEP 486 integration Jaikiran Pai
• Integrated: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection Jaikiran Pai
• Integrated: 8344525: Fix leftover ExceptionOccurred in java.base Justin Lu
• Integrated: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration Volkan Yazıcı
• RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration Volkan Yazıcı
  • Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration [v2] Jaikiran Pai
  • Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration [v2] Daniel Fuchs
  • Integrated: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration Volkan Yazıcı
• RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration Volkan Yazıcı
  • Re: RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration [v2] Jaikiran Pai
  • Integrated: 8344855: Remove calls to SecurityManager and doPrivileged in HTTP related implementation classes in the sun.net and sun.net.www.http packages after JEP 486 integration Daniel Fuchs
• Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Jaikiran Pai
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Daniel Fuchs
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Alan Bateman
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Jaikiran Pai
• RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java Eirik Bjørsnøs
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java Daniel Fuchs
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java Eirik Bjørsnøs
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java Eirik Bjørsnøs
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java [v2] Eirik Bjørsnøs
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java [v2] Andrey Turbanov
  • Re: RFR: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java [v3] Eirik Bjørsnøs
  • Withdrawn: 8344854: Modernize test/jdk/java/net/URLClassLoader/RemoveJar.java duke
• Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v3] Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v3] Jaikiran Pai
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v3] Jaikiran Pai
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
• Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v4] Volkan Yazıcı
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v4] Daniel Fuchs
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v4] duke
• RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Sean Mullan
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Alexey Bakhtin
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Sean Mullan
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Alexey Bakhtin
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Sean Mullan
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Alexey Bakhtin
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Sean Coffey
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Sean Mullan
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Sean Mullan
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Sean Coffey
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Anthony Scarpino
  • Re: RFR: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages [v2] Hai-May Chao
  • Integrated: 8344366: Remove Security Manager dependencies from javax.net.ssl and sun.security.ssl packages Sean Mullan
• RFR: 8344217: Remove calls to SecurityManager and and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration Roger Riggs
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration Alan Bateman
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration [v2] Alan Bateman
  • Integrated: 8344217: Remove calls to SecurityManager and doPrivileged in java.net.DatagramSocket and java.net.NetMulticastSocket after JEP 486 integration Daniel Fuchs
• RFR: 8344652: Remove access control context text from SSLEngine and SSLSession APIs Sean Mullan
  • Re: RFR: 8344652: Remove access control context text from SSLEngine and SSLSession APIs Jamil Nimeh
  • Re: RFR: 8344652: Remove access control context text from SSLEngine and SSLSession APIs Daniel Fuchs
  • Re: RFR: 8344652: Remove access control context text from SSLEngine and SSLSession APIs Sean Mullan
  • Integrated: 8344652: Remove access control context text from SSLEngine and SSLSession APIs Sean Mullan
• Re: RFR: 8344223: Remove calls to SecurityManager and doPrivileged in java.net.URLClassLoader after JEP 486 integration [v2] Alan Bateman
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
• Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v3] Volkan Yazıcı
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v3] Chen Liang
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v3] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Volkan Yazıcı
• Integrated: 8344236: Revisit SecurityManager usage in jdk.net after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp Sean Mullan
• Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v2] Jaikiran Pai
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344219: Remove calls to SecurityManager and doPrivileged in java.net.SocksSocketImpl after JEP 486 integration [v2] Volkan Yazıcı
• Re: RFR: 8344525: Fix leftover ExceptionOccurred in java.base Justin Lu
  • Re: RFR: 8344525: Fix leftover ExceptionOccurred in java.base Naoto Sato
  • Re: RFR: 8344525: Fix leftover ExceptionOccurred in java.base Iris Clark
  • Re: RFR: 8344525: Fix leftover ExceptionOccurred in java.base Justin Lu
• Re: RFR: 8344223: Remove calls to SecurityManager and doPrivileged in java.net.URLClassLoader after JEP 486 integration [v4] Yudi Zheng
• [RFD] Stray permission comment in sun.net.www.protocol.jar.JarURLConnection Eirik Bjørsnøs
  • Re: [RFD] Stray permission comment in sun.net.www.protocol.jar.JarURLConnection Jaikiran Pai
• RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted Daniel Fuchs
  • Re: RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted Jaikiran Pai
  • Re: RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted [v2] Daniel Fuchs
  • Re: RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted [v2] Jaikiran Pai
  • Re: RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted [v2] Daniel Fuchs
  • Re: RFR: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted [v2] Jaikiran Pai
  • Integrated: 8344346: java/net/httpclient/ShutdownNow.java fails with java.lang.AssertionError: client was still running, but exited after further delay: timeout should be adjusted Daniel Fuchs
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
• Re: RFR: 8344056: Use markdown format for man pages [v4] Magnus Ihse Bursie
• Integrated: 8344223: Remove calls to SecurityManager and doPrivileged in java.net.URLClassLoader after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344236: Revisit SecurityManager usage in jdk.net after JEP 486 integration Martin Doerr
  • Re: RFR: 8344236: Revisit SecurityManager usage in jdk.net after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344236: Revisit SecurityManager usage in jdk.net after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344236: Revisit SecurityManager usage in jdk.net after JEP 486 integration Varada M
• Re: RFR: 8344215: Remove calls to SecurityManager and doPrivileged in java.net.Socket and java.net.ServerSocket after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344215: Remove calls to SecurityManager and doPrivileged in java.net.Socket and java.net.ServerSocket after JEP 486 integration duke
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v8] Volkan Yazıcı
• Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v2] Sean Mullan
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v2] Brian Burkhalter
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v6] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
• Integrated: 8344215: Remove calls to SecurityManager and doPrivileged in java.net.Socket and java.net.ServerSocket after JEP 486 integration Volkan Yazıcı

• Later messages