forwardfor is for http only of course. You have the client and server timeouts set to 60 seconds which means that if those tcp connections are idle for that time the connection will be closed. Maybe that's not what you intended?
-Bryan On Thu, Jan 10, 2013 at 8:20 PM, B MK <[email protected]> wrote: > Hello, > > My rabbitmq connection dropped every minute behind haproxy. If i connected > directly there was no issue. I already mailed this issue on rabbitmq > mailing list. > http://rabbitmq.1065348.n5.nabble.com/Connection-error-on-RabbitMQ-consumer-behind-haproxy-td24348.html > . > > How to add this "option forwardfor" in tcp mode. Is it possible. > [WARNING] 010/095024 (902) : config : 'option forwardfor' ignored for > proxy 'rabbitmq_consumer_cluster' as it requires HTTP mode. > > > > See my haproxy configuration, > > global > log 127.0.0.1 local0 > log 127.0.0.1 local1 notice > #log loghost local0 info > maxconn 4096 > #chroot /usr/share/haproxy > user haproxy > group haproxy > daemon > #debug > #quiet > > defaults > log global > # mode http > # option httplog > option dontlognull > retries 3 > option redispatch > maxconn 5000 > contimeout 10000 > clitimeout 60000 > srvtimeout 60000 > > > listen rabbitmq_producer_cluster 0.0.0.0:5672 > mode tcp > > balance roundrobin > > server rabbit_1 rabbit1:5672 check inter 5000 rise 2 fall 3 > server rabbit_2 rabbit2:5672 check inter 5000 rise 2 fall 3 > #server rabbit_3 rabbit3:5672 check inter 5000 rise 2 fall 3 > > listen rabbitmq_consumer_cluster 0.0.0.0:5673 > mode tcp > balance roundrobin > option tcpka > > server rabbit_1 rabbit1:5672 check inter 5000 rise 2 fall 3 > server rabbit_2 rabbit2:5672 backup check inter 5000 rise 2 fall 3 > #server rabbit_3 rabbit3:5672 check inter 5000 rise 2 fall 3 > > listen private_monitoring :8100 > mode http > option httplog > stats enable > stats uri /stats > stats refresh 5s > >
