Example using streaming #1054

Activity

1. snicoll commented on Mar 2, 2023

   

   snicoll

   on Mar 2, 2023

   Author

   More actions

   The problem is that the request is "never" completed. I can reproduce this using the raw HttpClient, something like

   CloseableHttpAsyncClient client = HttpAsyncClientBuilder.create()
           .setDefaultRequestConfig(RequestConfig.custom()
                   .setCookieSpec(CookieSpecs.STANDARD)
                   .setSocketTimeout((int) Duration.ofSeconds(30).toMillis()).build()).build();
   client.start();
   HttpGet request = new HttpGet(createFilteredStreamUrl());
   request.addHeader(OAuthConstants.HEADER, "Bearer " + this.twitterClient.getBearerToken());
   client.execute(request, new FutureCallback<HttpResponse>() {
       @Override
       public void completed(HttpResponse httpResponse) {
           System.out.println("completed:" + httpResponse);
       }
   
       @Override
       public void failed(Exception e) {
           System.out.println("failed");
           e.printStackTrace();
       }
   
       @Override
       public void cancelled() {
   
       }
   });

   The completed callback is not invoked. And that makes sense since it's not flagged as completed:

   2023-03-02 13:26:52,023 [I/O dispatcher 10] DEBUG org.apache.http.impl.nio.client.InternalIODispatch - http-outgoing-1 [ACTIVE] [chunk-coded; completed: false]
   

   However, using the HttpAsyncResponseConsumer contract, I am able to do what I want. Have I missed something in the httpclient abstraction that allows this?