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

Solution Verified - Updated -


  • 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);
    ClientExecutor executor = new ApacheHttpClient4Executor(httpClient);
  • Why didn't the timeout apply to this?


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content