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
In the Java RI's CRLRevocationManager (in the agent), there is a URLConnection that has a connect timeout set, but no read timeout set, which defaults to 0 (which means infinite timeout). This can cause threads to be hung on line 364 (the last line in the snippet below):
// create a URL connection object from the distribution point
URLConnection urlConnection = new URL(crlUrlString).openConnection();
urlConnection.setConnectTimeout(CRL_FETCH_TIMEOUT);
// get the input stream
InputStream crlInputStream = urlConnection.getInputStream();
The text was updated successfully, but these errors were encountered:
leoclee
pushed a commit
to leoclee/nhin-d
that referenced
this issue
Apr 7, 2016
In the Java RI's CRLRevocationManager (in the agent), there is a URLConnection that has a connect timeout set, but no read timeout set, which defaults to 0 (which means infinite timeout). This can cause threads to be hung on line 364 (the last line in the snippet below):
The text was updated successfully, but these errors were encountered: