You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're seeing Logbook causing leased connections not to be released. See the following graph, showing the measurement for the Apache client pool (when it recovers is when the instance is rebooted):
Expected Behavior
Leased connections to be released.
Actual Behavior
Leased connections are not released. Eventually the instance runs out of available connections and becomes inoperative.
! org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection from pool
! at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.leaseConnection(PoolingHttpClientConnectionManager.java:316)
! at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$1.get(PoolingHttpClientConnectionManager.java:282)
...
Description
We're seeing Logbook causing leased connections not to be released. See the following graph, showing the measurement for the Apache client pool (when it recovers is when the instance is rebooted):
Expected Behavior
Leased connections to be released.
Actual Behavior
Leased connections are not released. Eventually the instance runs out of available connections and becomes inoperative.
Possible Fix
#1052
Steps to Reproduce
Details in #1052.
Context
We are unable to use Logbook due to this which is a bummer because we really like it. It has also caused some unexpected downtime for us.
Your Environment
N/A
The text was updated successfully, but these errors were encountered: