org.apache.commons.httpclient.HttpClient stuck on request

Question

I have that code :

 while(!lastPage && currentPage < maxPageSize){


            StringBuilder request = new StringBuilder("http://catalog.bizrate.com/services/catalog/v1/us/" + " some more ...");

            currentPage++;
            HttpClient client = new HttpClient(new MultiThreadedHttpConnectionManager());
            client.getHttpConnectionManager().getParams().setConnectionTimeout(15000);



            GetMethod get = new GetMethod(request.toString());

            HostConfiguration configuration = new HostConfiguration();

            int iGetResultCode = client.executeMethod(configuration, get);
            if (iGetResultCode != HttpStatus.SC_OK) {
                System.err.println("Method failed: " + get.getStatusLine());
                return;
            }
            XMLStreamReader reader
                    = XMLInputFactory.newInstance().createXMLStreamReader(get.getResponseBodyAsStream());
            while (reader.hasNext()) {
                int type = reader.next();
            // some more xml parsing ... 
            }
            reader.close();
            get.releaseConnection();
          }

Somehow the code gets suck from time to time on line : executing request.

I cant find the configuration for a request time out (not the connection timeout) , can someone help me maybe , or is there something that I am doing basely wrong ?

The client I am using.

Community · Accepted Answer · 2017-05-23 12:06:59Z

3

You can also set socket read timeou using setSoTimeout() but that is no guarantee either.

The only solution is to run the request in a different thread and interrupt the thread after timeout. You can use FutureTask to do this. See my answer to this question for examples,

java native Process timeout

edited May 23, 2017 at 12:06

CommunityBot

11 silver badge

answered Jun 13, 2010 at 12:20

ZZ Coder

75.7k30 gold badges139 silver badges170 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Michele d'Amico · Accepted Answer · 2015-03-26 12:53:40Z

-1

PoolingConnectionManager maintains a maximum limit of connection on a per route basis and in total. Per default this implementation will create no more than than 2 concurrent connections per given route and no more 20 connections in total. For many real-world applications these limits may prove too constraining, especially if they use HTTP as a transport protocol for their services. Connection limits, however, can be adjusted using HTTP parameters. For more information, you can refer to PoolingClientConnectionManager Java API

edited Mar 26, 2015 at 12:53

Michele d'Amico

24.1k10 gold badges78 silver badges78 bronze badges

answered Mar 26, 2015 at 8:03

Jackie Dong

8131 gold badge5 silver badges20 bronze badges

1 Comment

DavidPostill Over a year ago

Please explain how this answers the question, which is "I cant find the configuration for a request time out"

Collectives™ on Stack Overflow

org.apache.commons.httpclient.HttpClient stuck on request

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related