Name: dbT83986 Date: 02/02/99
Hi, I think more info should be added to the
SocketException to let the user know what went
wrong. The info should at least include the
following:
* What winsock api (or whatever platform-specific
socket api) was called
* What error code was from the failing api
This will help the user to locate the problem.
Thanks.
(Review ID: 37991)
======================================================================
- duplicates
-
JDK-4365572 Win32 winsock errors should be translated to error message text
-
- Resolved
-