You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2020. It is now read-only.
The exception handling (or rather, printing) code in BaseClient.issueGet() and BaseClient.issueDelete() invariably ends up throwing IOExceptions, obscuring the actual exception that occurred.
Sequence of events looks something like:
readFromConnection gets response code higher than 400
readFromConnection constructs StringBuilder with message from connection
readFromConnection's finally block closes the InputStreamReader
Closing an InputStreamReader closes the underlying stream.
readFromConnection throws newly constructed IOException with helpful message
issueGet (or issueDelete) catches the IOException
issueGet tries to read from the connection's error stream (which is already closed)
issueGet throws new IOException with no information except "stream is closed"
The text was updated successfully, but these errors were encountered:
The exception handling (or rather, printing) code in BaseClient.issueGet() and BaseClient.issueDelete() invariably ends up throwing IOExceptions, obscuring the actual exception that occurred.
Sequence of events looks something like:
readFromConnection
gets response code higher than 400readFromConnection
constructs StringBuilder with message from connectionreadFromConnection
'sfinally
block closes theInputStreamReader
InputStreamReader
closes the underlying stream.readFromConnection
throws newly constructedIOException
with helpful messageissueGet
(orissueDelete
) catches theIOException
issueGet
tries to read from the connection's error stream (which is already closed)issueGet
throws newIOException
with no information except "stream is closed"The text was updated successfully, but these errors were encountered: