Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-255

Timeouts when using the ProxyHandler and LoadBalancingProxyClient don't release the connection


    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 1.1.Beta1
    • Fix Version/s: 1.1.Beta2
    • Component/s: Core
    • Labels:


      When using the ProxyHandler with the LoadBalancingProxyClient, timeouts due to long processing on the eventual endpoint leave the Http connection open on the proxying server.

      Service layout:

      Service 1 - This is the service that uses the ProxyHandler with the LoadBalancingProxyClient.

      final ProxyHandler proxy = new ProxyHandler(new LoadBalancingProxyClient()
      .addHost(new URI("http", null, host, port, null, null, null), (String) null),
      timeout /* 3600 */, ResponseCodeHandler.HANDLE_404);

      Service 2 - This is the service that has that eventually handles the request. If this consumes more time then the proxy timeout then the Http connection to the caller of Service 1 is never released.


      When the proxy timeout is triggered it runs through the code at ProxyHandler->handleRequest() (line 133) where the comment "we rely on the close listener to end the exchange" states that the connection will be cleaned up by the close listener.

      The cleanup code in the ProxyConnectionPool->openConnection() (line 172) is called. This releases the connection back to the pool, but the exchange is never ended and thus the caller is left hanging.

        Gliffy Diagrams




              • Assignee:
                swd847 Stuart Douglas
                vonnagy Ivan von Nagy
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: