This would be especially useful in asynchronous applications - since in
those cases the exception rarely maps back to a place in user code that
would indicate what is being connected to. As someone who has spent a lot
of time supporting developers who use asynchronous libraries and post
exceptions
Hi All,
I am wondering if it would be possible to make a minor improvement to the
way *java.net.Socket* reports connectivity errors and incorporate the
attempted address, port and the timeout used into the exception message.
The current implementation emits a generic error message, which is not
