RFR: 8336815: Socket.bind/connect and ServerSocket.bind/accept do not specify behavior when already bound, connected or closed [v3]

Jaikiran Pai jpai at openjdk.org
Sat Jul 20 14:40:57 UTC 2024


> Can I please get a review of this change which updates the specification of a few methods in `java.net.Socket` and `java.net.ServerSocket` classes to specify the `IOException` that the implementation currently already throws?
> 
> This is merely a doc update and doesn't change the implementation.
> 
> Given that these exceptions can now be asserted, a new jtreg test has been introduced to verify the exceptions thrown from these APIs. The test passes. tier testing is currently in progress. I'll open a CSR shortly.

Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision:

  update specification on few other methods to match the implementation and also update test to verify the expectations

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/20268/files
  - new: https://git.openjdk.org/jdk/pull/20268/files/8990787f..957fa7ec

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=20268&range=02
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=20268&range=01-02

  Stats: 623 lines in 5 files changed: 426 ins; 142 del; 55 mod
  Patch: https://git.openjdk.org/jdk/pull/20268.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/20268/head:pull/20268

PR: https://git.openjdk.org/jdk/pull/20268


More information about the net-dev mailing list