# \[Solved\] HAProxy start adding to queue even if maxconn is not reached

**URL:** https://discourse.haproxy.org/t/solved-haproxy-start-adding-to-queue-even-if-maxconn-is-not-reached/103
**Category:** Help!
**Created:** [February 12, 2016, 9:03am UTC](https://discourse.haproxy.org/t/solved-haproxy-start-adding-to-queue-even-if-maxconn-is-not-reached/103 "2016-02-12T09:03:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![covidium](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/covidium/32/30_2.png) [@covidium](https://discourse.haproxy.org/u/covidium)
#### Post date: [February 12, 2016, 9:03am UTC](https://discourse.haproxy.org/t/solved-haproxy-start-adding-to-queue-even-if-maxconn-is-not-reached/103/1 "2016-02-12T09:03:36Z")

</div>

Hi All.

For some time, I’m trying to figure out why Haproxy begins to queue even if the number of maxconn hasn’t been reached. I think I’ve tried all the possibilities to configure and reconfigure it and still haven’t got an result.

The implementation is like this: web server \<\> HAProxy \<\> database server .

Everything seems to work just fine, the haproxy works properly until it reach a point when starts to queue, even if the database server supports more than 200 concurrent queries. For test purposes, I’ve made 40 concurrent queries to that server, but at some point the haproxy queue begin to increase. Here is the log of that test [http://pastebin.centos.org/39671/55266771/raw/](http://pastebin.centos.org/39671/55266771/raw/) and as you can see, after the 20th query begins to queue.  
The configuration is this [http://pastebin.centos.org/39676/67677145/raw/](http://pastebin.centos.org/39676/67677145/raw/) .

Most likely there is something that I miss but cannot figure out what.

Thank you for your time.

---

<div class="post-metadata">

### Author: ![Baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@Baptiste](https://discourse.haproxy.org/u/Baptiste)
#### Post date: [February 12, 2016, 11:00am UTC](https://discourse.haproxy.org/t/solved-haproxy-start-adding-to-queue-even-if-maxconn-is-not-reached/103/2 "2016-02-12T11:00:40Z")

</div>

Please remove the minconn parameters and refer to the documentation of the parameters below:

[http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#minconn](http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#minconn)  
[http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#fullconn](http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#fullconn)

---

<div class="post-metadata">

### Author: ![covidium](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/covidium/32/30_2.png) [@covidium](https://discourse.haproxy.org/u/covidium)
#### Post date: [February 12, 2016, 12:38pm UTC](https://discourse.haproxy.org/t/solved-haproxy-start-adding-to-queue-even-if-maxconn-is-not-reached/103/3 "2016-02-12T12:38:22Z")

</div>

@Baptiste - Thank you so much for this information. You’ve made me very happy.  
Thank you again very much.
