Why is connection timeout not applied to RESTEasy client in EAP 6 / 5 ?

Issue

• One of our EAP cluster nodes doesn't process a RESTEasy client's calls for couple of days and start to work only after restart.
• According to the thread dump, it shows that the thread is hanging (in runnable state) in the middle of the RESTEasy client code.

• Here is part of the RESTEasy client code. While creating the request executor we are passing the connection timeout, but not sure why the timeout didn't apply to this instance.

  HttpClient httpClient = new DefaultHttpClient();
  HttpParams params = httpClient.getParams();
  HttpConnectionParams.setConnectionTimeout(params, 5000);
  httpClient.setParams(params);
  ClientExecutor executor = new ApacheHttpClient4Executor(httpClient);
  

• Why didn't the timeout apply to this?