Project

General

Profile

Bug #1777

d1_libclient_java blocks on read

Added by Robert Waltz over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
d1_libclient_java
Target version:
Start date:
2011-09-09
Due date:
% Done:

100%

Milestone:
CCI-0.6.4
Product Version:
*
Story Points:
Sprint:

Description

Due to a misconfiguration of tomcat and programmatic error, a 404 error with a resulting error message causes the d1_libclient_java's use of d1_common_java's ExceptionHandler to block while executing the input stream read (IOUtils.toString(errorStream)) in deserializeHtmlAndThrowException.

Setting CONNECTION_TIMEOUT and SO_TIMEOUT on the apache DefaultHttpClient did not help.

History

#1 Updated by Rob Nahf over 10 years ago

  • Status changed from New to In Progress
  • Target version set to Sprint-2011.36-Block.5

Robert reports that the new timeout settings in RestClient are working for him now. Going to keep this open as a reminder to clean up and parameterize the timeouts.

#2 Updated by Dave Vieglais over 10 years ago

  • Target version changed from Sprint-2011.36-Block.5 to Sprint-2011.37-Block.5
  • Position set to 13

#3 Updated by Rob Nahf over 10 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

added setTimeouts(milliseconds) to D1RestClient and RestClient.
Gave a default value of 30 seconds to the client.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)